the 'tuned-updates' option in jaws.xml is pretty critical - it prevents
wasting time updating the database with data that hasn't changed.
You can also impliment an 'boolean isModified()' method on your entity
beans that returns false if nothing changed. This will allow JBoss to
bypass even chec
Naresh,
please have a look at the "JBoss in production" chapter in the manual.
There is also a special "Performance" section.
If you are already testing I would be really interested in hearing if
switching between the native_ and green_thread implementation of the JDK
gives any performance differ
Hello Everybody,
I have wrote a small application having 2 CMP beans and 1 session bean
in it. Now i am testing the performance and resource consumption of
application servers using this application. so i have deployed this
application on JBoss 2.2.1 version and starting 25 client, each firing
10