RSA7 and Local WebSphere Test Environment Performance Tips

If you’re encountering slowness in either your RSA IDE or in the embedded WebSphere Test Environment, here several strategies that may help:

 

RSA7 Performance

• In c:\Program Files\IBM\SDP70\jdk\bin run this: “java -Xshareclasses:destroyAll”.  This will delete a cache file in C:\Documents and Settings\<username>\Local Settings\Application Data\javasharedresources.
• Run “C:\Program Files\IBM\SDP70>eclipse –clean”  This is supposed to clean up some other cached data.
• Edit eclipse.ini (C:\Program Files\IBM\SDP70\eclipse.ini) to change the “-Xshareclasses:singleJVM,keep” line to “-Xshareclasses:none”
• Edit eclipse.ini to have larger max heap (e.g. 768m), and set min heap equal to max.
• Try increasing the MaxPermSize in eclipse.ini (e.g. 512M).
• Update RSA7 to the latest fixpack.
• Try disabling automatic build; use Ctrl-B instead.
• If using JIBX, try removing the JIBX compiler from the  builder list and running manually when needed.
• Try disabling the “AOP Reference Model Builder” builder if you’re using Spring IDE. 

WAS 6.1 Test Environment Performance

• Update the WAS test env to the latest fixpack.
• Verify that automatic publishing is turned off.
• Restart applications via the “Restart” menu option instead of the “Publish” option on the application server.
• Set the min / max heap for WAS JVM to same size and larger, like 768 or 1024

Both

• Be aware that virus scan real time protection on most computers will significantly degrade disk IO.   Also be especially careful that no scheduled scan is currently running.
• Also beware that laptops running PointSec full disk encryption can expect at least a 50% degradation in disk IO performance vs. a non-encrypted file system.
• If you have at least 3GB of memory, try reducing paging file size to very low to minimize paging.