Multiple concurrent connections

Grizzly must be dealing better with those, and it is. The test script for this particular run was generating a 200 kB page in several chunks, pausing a little in between to reach total of 30 seconds. Up to 200 concurrent open connections were observed on the server, with Grizzly loading the CPU to 13-14% vs Tomcat taking 15-16%. Difference is not that great, but I hope to exaggerate it by increasing and adjusting the load.

On another note, I start to like console of Glassfish more and more, as I get accustomed to its terms (i.e. what which pool means). Capability to monitor running processes is very convenient.

Tomcat vs Grizzly, first run

Oopsy-daisy! Same workload (GET static XHTML file 60 kB) produced same throughput figures (ran 25 minutes, 64-bit JDK 1.5_04 on Solaris 10), but it took Tomcat less CPU to start up and do the work, than Glassfish to start up alone. That is probably meaningless, but it also took Tomcat under 30 seconds of CPU time to process same workload that took Glassfish 58. I must have misconfigured something somewhere, that can not be right... I'm certain I allowed Tomcat to use up to 500 threds to process incoming request, did no such thing for Glassfish. Should I take a look at memory use? Since Glassfish by default uses less threads (a note, Tomcat would start sending "out of service" messages under same conditions), how does that make Glassfish use more CPU but guarantee same service level?

UPDATE: although it takes Glassfish a fair bit longer to reach performance plateau under load, it eventually ends up exactly at the same CPU utilization as Tomcat in this particular test. The question remains, how do I tweak configuration of both Tomcat and Glassfish so that I see the benefits of NIO connector (if any)...

Life is messy, but so should not be one's blog

I should break my blog into several thematical blogs. The way AdSence works, it's plain silly to mix notes on politics, technology and life in general. It simply does not make for a meaningful read to whoever could wind up on my blog...