Caching and connection pooling are good.  But sometimes it is just a question 
of looking at your application and using jBPM appropriately. 
For example, you must consider paging when huge recordsets are returned. In any 
case, you will not be able to display thousands of records to the user. So why 
get all of them in one stretch.

Simple changes like these to your business process layer can make your 
application blazingly fast.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913614#3913614

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3913614


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to