I've spent the day running some test similiar to Paul's. My environment is Linux on a PIII 500, running Sun's 1.3 and 1.3.1beta JDKs. In the case of a standalone client looping and repeatedly calling the same method on a stateless session bean, I found that Orion averaged about 3ms. per invocation where JBoss was averaging 6-10 ms/invocation. There was no logging output from either app. server or the beans. Something interesting about the spread of numbers in JBoss' case is that the low numbers were where it was running off of a local drive, whereas the high numbers where off of an NFS share. What prompted me to make that shift (from NFS in my home to a local /usr/local) was seeing some classloader and unix filesystem activity with very high 'count' values in a hprof output (from 'java -Xrunhprof' that is). At any rate, it seems that something in JBoss might be hitting disk a bit more than i'd expect once it gets into a steady running state: shouldn't classes be loaded at that point? Is it possible that some configuration of classloaders is still searching jar files even when the class is loaded? Paul, had you written tests where the bean actually did work? I'm curious to see if the ~3-6 second differention in invocation times is a constant or not. I also made a servlet which performs an equivalent test in-VM. This was even more disturbing, with Orion taking 10-50 ms to perform 5000 invocations and JBoss/Tomcat taking 2250 or thereabouts. This is such a huge difference that I have to believe that optimized invocations are broken in my configuration. At this point, I'm about at the end of what I can find from the standard runhprof output. I'm trying to get JProbe installed, but that isn't going all that well. I should be able to post my client and bean tommorrow, if anyone is curious. thanks, danch Fink, Paul wrote: > Oh sorry I should have said. > > Jboss 2.1 binary (down loaded March 22) > > Orion is 1.3.8 > >> performance dependent the JBoss version ran very slow. After playing > > with > >> cache setting, etc. It seemed like the communications was the main > > bottle > >> neck. >> To test this I wrote a simple session bean with one get method that > > returns > >> a Long. >> >> The client looped 10,000 times calling the getter. The Orion version > > was 6 > >> times faster! >> Other tests we ran had Orion running 4x faster. >> >> It seems that JBoss certainly is performance limited. >> >> I'm running on a 900 MHz PIII under Linux with Sun's JDK 1.3 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-development
