results.text

I ran the same test 5 times, and this is the median result for Reverse 
routing. While the numbers may vary in small amounts, the wins in 
parse() are very signifcant.

In the store test, I did not try named routes, as this set of routes 
was intended to stress test the parsing/matching changes.

------------------------------------------------------

Book Routes - 3.0 HEAD
Reverse routing URLs took 1.7574610710144
Reverse routing with named routes took 2.1541481018066
Parsing URLs took 77.649255990982

Book Routes - prototype
Reverse routing URLs took 1.6308670043945
Reverse routing with named routes took 1.6077740192413
Parsing URLs took 42.100316047668

------------------------------------------------------

Store routes - 3.0 HEAD
Reverse routing URLs took 6.7904450893402
Reverse routing with named routes took N/A
Parsing URLs took 185.72615599632

Store Routes - prototype
Reverse routing URLs took 2.4322938919067
Reverse routing with named routes took N/A
Parsing URLs took 14.599720001221