Hi again, Thanks for the reply. I have run some more tests. for these I have set the memory consumption of the stateless server beans to zero and I increased the number of users to 100 (all running the same single method transaction). there are also 100 beans in the pool. What I would expect to find is that as we increase from 1 thread up to somewhere near 100, we should get increasing throughput and decreasing response times, but quite the opposite is happening (see below). Regarding context switching, surely JBoss should only switch between threads when there is something active on the thread and should not switch to threads that are not in use (and so unused threads shypould not cause extra runtime CPU usage (or a very minimal amount to check the extra threads for usage???)
Thanks again for any insight provided Regards, David RESULTS ==================== Threads RT TP 1 87092 132 5 84231 142 10 95694 111 25 90989 129 50 101541 116 100 132768 99 ===================== View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869013#3869013 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869013 ------------------------------------------------------- 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
