JBoss Jetty performance with Mulitple users

[stephenw]

Hi,
Im currently running some performance tests.
Configuration :-
JBoss 2.4.4
Jetty 3.1.7
Application consisting of approx 15 BMP entity beans and 5 SessionBeans ( Stateless ).
Utiliseing VO pattern.
Oracle Database.
Servers we've tried:-
NT 500mhx 1.2gbram
Solaris double processor 1.2gb ramHP Unix 4 processors 3GB ram

So the scenerio is that we want to test 1000 users bombarding the application, for this we're using Rational Robot which seems to be ok.
But was wondering if any one has any tips for configuration files which are currently set with:-
standardjboss.xml :-
beanpool = 2000 (BMP)

jboss.xml
max dbpool size = 100

Jetty.xml
maxthreads = 1250

The test case for each user is very simple, login search for data select an object move on etc , no updates or saves. Also giving a good time inbetween actions.

Look forward to tweak and any other advice.

So far we've had good results on the HP machine, 1000 users, memaround 700mb and only useing 2 cpus,
On the sun and NT box both seem to get extremely stuck after 500 users, impossible to log on etc..

Also its interesting to note that all machines dont max out on the cpu ( nt around 70% avg, sun going upto 50% on secound cpu) and memory seems to be fine set at around 700mb.

Look forward to your help,
Stephen.

[sammy-t]

Here is the meat, of the sudden death of Jboss 3.2.2 running on redhat 9. I had redirect the entire jboss console output in order to capture this information.


#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode)
# Error ID: 43113F32554E54494D45110E4350500308
# Problematic Thread: prio=1 tid=0x4752a018 nid=0x75c8 runnable
#
Heap at VM Abort:
Heap
def new generation total 2304K, used 1124K [0x4ac10000, 0x4ae80000, 0x4b0f0000)
eden space 2112K, 45% used [0x4ac10000, 0x4ad02438, 0x4ae20000)
from space 192K, 80% used [0x4ae50000, 0x4ae76c08, 0x4ae80000)
to space 192K, 0% used [0x4ae20000, 0x4ae20000, 0x4ae50000)
tenured generation total 28576K, used 16359K [0x4b0f0000, 0x4ccd8000, 0x4ec10000)
the space 28576K, 57% used [0x4b0f0000, 0x4c0e9ff0, 0x4c0ea000, 0x4ccd8000)
compacting perm gen total 17664K, used 17442K [0x4ec10000, 0x4fd50000, 0x52c10000)
the space 17664K, 98% used [0x4ec10000, 0x4fd18be8, 0x4fd18c00, 0x4fd50000)
~

[tisi]

You're overwhelming the VM. Sun's VM maps threads to POSIX threads and is known to have problems with more than a few hundred.

Scale down Jetty's threadpool to 250 or go for a VM with a different thread implementation. BEA has just acquired JRockit and gives it away for free.