MVC Beta 1 Routing - how many routes will start to cause performance issues?

I am looking at preloading routes to static content pages, allowing n-depth of content nesting. I have a solution that provides a bit of comfort in terms of the number of potential routes registered, but I'm wondering if the system is too complex.

How many logged routes do you suspect the underlying hosting account will start to suffer from performance issues? These routes are purely textual, with no need to parse values.