MVC Beta 1 Routing - What Number Of Routes Will Start To Cause Performance Issues?
I am considering pre-loading routes to static content pages, allowing for n-depth nesting of content. I have a solution spiked that provides a bit of comfort in terms of the number of potential routes registered, but I'm wondering if I'm making the system overly complex.
At what number of registered routes do you suspect a basic hosting account would start to suffer in performance? These routes are pure-text, with no need to parse values.
Route-parsing, compared with database access? I would guess the route-parsing is pretty cheap. Until you get into the thousands of routes.
- → Function Undefined in Axios promise
- → AngularJS directive: "templateUrl" doesn't work while "template" works
- → URL routing requires /Home/Page?page=1 instead of /Home/Page/1
- → NumericTextBox Loses Value using Html.TextBoxFor, not HTML
- → Does the fact that every page is reachable through www.example.com and www.example.com/index have any SEO impact?
- → SEO tags in Umbraco
- → Add dynamic divs around 6 image urls using jquery
- → ASP.NET Mvc 5 return View with seo friendly url
- → MVC SEO targeting Italy from a .uk.com domain
- → Using an object I never defined in JQuery
- → Pass json data from Google Maps to MVC controller with AJAX
- → Displaying Unique SEO code two times in the URL when change length 2 to 5