On 02/15/2010 12:30 PM, Steve Ryan wrote:
Are there any known performance issues with the Tomcat JK redirector, in particular, any performance issues which could affect the third-party websites as explained in my example above?
Since this is filter it will participate in every request. Now this might sound scary but the actual participation is limited to matching the url with the uriworkermap.properties list. Depending on the rules used this might be as simple as a few strcasecmp operations or few regex matchings, but on any decent hardware this should be very fast. How fast, well to get a precise number you will have to measure it, but it should be fast enough so it won't be measurable without using high performance timers. Of course there are few other operations involved with each request, and the largest performance degradation will be involved with logging if you use debug level since this will force writing to the file for each request even the one not going trough isapi_redirector. However using debug logging might be worse-case scenario proof of concept since you will have in the logs the amount of time spend for each request inside isapi_redirector, so it will give you the sense of the performance degradation. Of course this time will include the time for actual logging, so the production timing would be much less. Regards -- ^TM --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
