I am looking into some options for url rewriting in a .NET app. Since each page that my app handles already has the potential to be somewhat processor intensive (depending mostly on the number and depth of navigation links that must be dynamically built with each page load), I&#039;m wary of anything that might create an additional hit on performance.<BR><BR>For example, I have links like "default.aspx?id=34&someval=test" that I want to convert to something like "/?id=34&someval=test/about-us/<BR><BR>Where the page with id 34 is actually the about us page. But there may also be some querystring params that the page needs. What is the relative performance hit when these techniques are used to modify the url in this way vs the raw url?<BR>