Costin Manolache wrote:
I believe I did some tests at that time and didn't seem so bad.
It's not like it's going to read the strings/files on each request -
it's loading them
once, and will stay in memory for all the 'hot' jsps. The difference between a
static final String access and a loaded String is not that big, and
for GC - it'll
get to the old generation quite soon.
Do you have any test - or technical reason - why it would be 'really bad' ?
I'm very interested - it's allways good to learn new things about GC...
In any case - my thinking at that time was that this should be the
default mode for 3.3 if it matures. Not sure what was the exact
benchmark I used - but I was quite obsessed with performance.
I believe serving multiple uncached small files as part of a single
request will have bad performance. If using properties files, pre
request parsing will be involved, which seems costly. I don't see how to
avoid this issue.
Well, that would probably be bad for tomcat - and longer term bad for
your own tree :-)
There are a lot of valid reasons to contribute - or not contribute -
to a project.
Actually, for the rest of the code, it goes really well so far.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
