https://issues.apache.org/bugzilla/show_bug.cgi?id=55511
--- Comment #7 from Jason Koch <jas...@bluedevel.com> --- Just adding an additional comment - trailing from my blog - in case somebody else comes across this and wants to open it up. In my opinion this will become an issue for someone in the future, but I wasn't able to hook up a suitable test to prove it. Hopefully somebody else can. http://fasterjava.blogspot.com/2013/08/caching-classes-from-classloader.html ===== Hi Ryan - totally agree with you. TC classloader is definitely a source of contention, but I was unable to come up with a real-world scenario where it affected throughput. If you have enough of a test bench you can probably re-run the tests and see how it goes, I'd be keen to hear about it. I assume you are looking at Tomcat? What I found is that when I used the default Tomcat classloader in a real world scenario (about 2000req/sec incl business logic, db query, output transform, etc), changing the classloader did not significantly affect the req/sec rate. It only changes it when running under the profiler or under contrived examples - eg calling loadClass in a tight loop. I don't have the test bench to drive enough load onto the server - I was able to saturate the NIC before running out of CPU. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
