jboss 3.2.2 worse performance than jboss 2.4.x

[javierpaniza]

Hi,

we have migrate from jboss 2.4.6 to 3.2.1, and then from 3.2.2

The good is that 3.2.2 is more faster than 3.2.2, but
is more, more, more slow than 2.4.6.

Using a real code that run in our clients, the same process:
- jboss 3.2.1: 160 seconds.
- jboss 3.2.2: 120 seconds.
- jboss 2.4.6: 60 seconds.

that use CMP 1.1, JDBC, with commit-option B (is necessary)
and marking methods gets read-only (in jboss.xml)

How is this possible?
Any idea to optimize jboss 3.2.2 for run equals
than jboss 2.4.6 without migrating to ejb2.

[jonlee]

The CMP 1.1 engine does have scalability issues and the additions for bug-fixes have cleaned up the bugs but inevitably add a bit of delay. However, it is probably not the primary cause of the performance issues you see. Since 3.2.x adds many more features in-line with the expanding requirements of the J2EE spec, you have quite a few more services operating. Try removing services you don't use to cut down threads and background processes. Also, if using Windows I believe there are some additional tweaks related to the poor handling by the OS of incoming network requests. You should be able to find the tips scattered through this forum or on the mailing list. Also create an optimized build.

Hope this helps.

[javierpaniza]

Hi,

I win that jboss 3.2.2 run faster that 2.4.6.

I changed various configuration parameter, but
for me, put read-ahead to true, boost the performance
a lot.

Here the results of my tests (using real code, no test code):

3.2.2tunned 3.2.2original 3.2.1 2.4.6
----------------------------------------------
1 8630 12780 22258 20853
2 7322 11273 18077 7533
3 6991 13697 19492 7945
----------------------------------------------
4 14415 28126 35292 17255
5 10609 24180 32050 10517
6 11930 28342 33865 12071
----------------------------------------------
59897 118398 161034 76174