Costin Manolache wrote:
Why would anyone serve 'uncached small files' or parse properties on each request ??? Well, maybe that was the (incomplete) implementation long ago - and I agree, it would be really bad for performance.
If you have more than 100MB of JSPs, I think the request distribution is going to be well spread out.
The static file can be loaded in init(), in a cache ( LRU or more complex, or just a weak reference ) - if the jsp is not used for a long time and the strings get GC, it'll have a small hit on the next usage - similar with the initial load. And it might have a small impact because of the cache and the weak reference versus final Strings. But I think it may compensate in other area - the memory is a very unpredictable thing, I've seen many cases where reducing the pressure and having more free space is faster than keeping everything in memory when the load is high ( because hight load usually means a small portion of the code is hit hard, and makes use of the extra memory, etc )
Yes. Nowehere else could I see the need to refactor, complexify and add bugs to cater to edge cases and improbable scenarios. The power of OSS (or at least, ASF's take on OSS).
Anyway - there is no point trying to predict how performance will be affected, if there is a patch it's easy to check.
Sure. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
