Netweaver Developer Studio 7.0 performance problem

Question

Hi everyone:
I have a situation in which I am unable to perform any operations upon opening a particular Edit Model Binding window. The number of nodes (25) & attributes (on average, 25 per node, several up to 100 per node) to be managed is so huge, that for any context mappings between the applicable model context and any of its 4 dependent contexts, NWDS 7.0 suffers from a 30-60 second delay when I try any kind of scrolling, opening and collapsing of nodes (sometimes even longer), even bringing up the window itself. The javaw.exe memory footprint from NWDS 7.0 becomes unmanageably large (500+ MB), paralyzing my whole computer even with 2GB RAM. From your own experiences, how did you manage doing any kind of Java Webdynpro context binding for such heavily populated Model contexts?
Any tips for resolving this issue in NWDS 7.0? Would upgrading to NWDS 7.1 help? Anybody conduct an informal performance comparison, memory requirements, and other benchmarks between the two IDEs? How would I maintain any outstanding activity requests from NWDS 7.0 I have not checked-in yet?
Please advise,
Jon

Answer 1

Hello Jon,
I agree, but 2 GB RAM is sufficient to run the NWDS efficiently, consider the following points to increase its performance.
1. Tweak your eclipse.ini : This will increase the memory usage of Eclipse, but will give you the best startup and working  performance. If you think eclipse is using up too much memory, lower the Xms, Xmx and PermSize values.
-startupplugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar--launcher.XXMaxPermSize256m-vmargs -Xms256m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+AggressiveOpts-XX:+StringCache-XX:+UseFastAccessorMethods-XX:+UseLargePages-XX:LargePageSizeInBytes=4m-XX:AllocatePrefetchLines=1-XX:AllocatePrefetchStyle=1-Dide.gc=true
2. Disable the un-necessary startup plugins
It loads up certain (un-necessary) plugins at startup. We can tweak this a bit to improve the startup performance.
Go to Window > Preferences
Expand General and select Startup and Shutdown
On the right side, uncheck the plugins you don't want to start. Usually, you can uncheck all of them. Don't worry, it just makes the startup minimal. Once you need to access the module in the IDE, it will start it up.
Click OK and restart IDE.
BR
Satish Kumar