I may have some info that bears on this... I have been performance testing the same app for 2 months with option #3 - Tomcat5/Apache in front, RMI to JBoss in back, JBoss to DB behind that.
Tomcat on Apple G5: 2CPU, 2G Ram, JBoss on Windows2000 4CPU,4G Ram, MySQL on Apple G5: 2CPU, 2G Ram. Most web pages are JSP, and the ones that aren't are served by a Dispatcher servlet. All JBoss communication is thru stateful and stateless EJB facades, Entity beans are local only, BMP, CMT. Current results indicate that RMI gets extremely slow as the load increases in Tomcat. Adding a user session every 2 seconds up to 500 concurrent requests causes EJBHome lookups alone to exceed 30s, and another 30s for create(). The AppServer and DB barely feel it at all. JBoss stats indicate that the create() never exceeds 250ms. Tomcat is chewing ~90% of the cpu within 2 mins of the test (120 users), but I can't tell exactly where its happening, although 85% of processing time is spent accessing and executing EJBs. Memory is quite tolerable, and Garbage Collection never exceeds 4% of processing time (-XX:+UseParallelGC). I don't know enough about jk2 Connectors to comment, but RMI isn't cutting it! To discuss directly, write me at [EMAIL PROTECTED] Hope this helps. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867013#3867013 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867013 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
