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 checking to see if the values of CMP fields have changed.
'isModified' is jboss specific (I believe it will work in weblogic as well)
-danch
Naresh Sharma wrote:
> 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
> 1000 operations(like Add bean) concurrently on the server.
>
> I did'nt modify any default setting in JBoss related to performance, Is
> it ok ?? or should i change some settings for better performance ??
>
> please let me know
>
> Thanks
> Naresh
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
