Last post Aug 08, 2007 06:11 PM by rstrahl
Aug 08, 2007 04:03 PM|Curt_C|LINK
I'm following the example from
I'm testing this in my local environment and it seems SLOW. I was previously using the Application_BeginRequest() method, manually parsing the URL, and this worked ok but it seems a bit klunky so I switched. Now I haven't pushed this up to my server environment
yet but with my dev it seems a LOT slower.
Is this the case? Is the HttpHandler method for UrlRewriting (without a custom ISAPI) considerably slower or is it just me?
Anyone else have perf issues with this?
Aug 08, 2007 06:11 PM|rstrahl|LINK
Define slow <s>... Have you actually run any perf testing on this?
In a low volume environment I doubt that you could tell any performance differences. However in high volume environments Regular Expression parsing etc. can become noticable because it's often very CPU heavy. Often switching to precompiled RegEx expressions
can help performance considerably. I didn't look at Scott's code, but I suspect it's probably not pre-compiling RegEx expressions.
I think it's also better to plug any UrlRewriting as early in the pipeline as possible certainly before a handler fires. You mention a Handler in your post? The code in the article describes a module. Certainly if you use an HttpHandler you have to transfer
operation to another URL which is somewhat inefficient. But if you're using a module all your doing is rewriting the URL which should be very fast.
When in doubt dig out a Profiler and take a look at what's actually slow.
+++ Rick ---