Hi,
Somebody reported a peformance problem in the forums that
is caused by inefficient loading of resources.
With xerces in server/default/lib, they do
new DomParser(...),
this leads to a
getResource("META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration);
from the ejb's classloader.
This searches all jars in server/default/deploy and server/default/lib
caching the result against the xerces UCL where it is located.
The next request goes through the whole search again until it spots
the cached version against xerces.
The results for 1000 document parses (repeated 5 times in millis)
37204, 30764, 29743, 29563, 29493
If you put xerces in the JBOSS_CLASSPATH the results are:
20820, 14571, 13369, 12578, 12658
Does anybody have a problem with adding a cache for these global
searches?
The logic will be:
Check the current classloader's cache
Ask the current classloader
Check the global cache <-- New bit
Ask the repository (all classloaders, result goes in global cache)
Not Found
This gives the results:
25396, 16374, 16113, 14852, 14541
About twice as fast once hot-spot kicks in.
Full testsuite in progress...
Regards,
Adrian
p.s. I probably won't respond to any reply until tomorrow
_________________________________________________________________
Join the world�s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
