Re: WDSC Performance

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Englander, Douglas
Sent: Thursday, April 24, 2008 12:18 PM
To: 'wdsci-l@xxxxxxxxxxxx'
Subject: [WDSCI-L] WDSC Performance



Does anyone know how I can determine what is causing my PC's processor to run at 95%+ at certain times when I am using WDSC? It seems to happen randomly, I cannot seem to track it, but it always seems to happen when I open the first source member I want to edit for the day. It can also happen while I am editing any member, but it almost always seems to happen when I open the first member after I start it up. Yesterday, every keystroke I typed in WDSC caused the PC processor to max out.
<snip>

I've seen this in Eclipse (but not to the same extent) and in jDeveloper as well the first time a specific editor is opened. My PC has a dual core processor so it usually doesn't go higher than 50% but the delay is far, far worse when I'm using the RPG editor. One thing I've found that makes it more tolerable is to leave a source member open in the editor when I shut down. This causes all the delay to happen during startup which to me is more tolerable than having to wait after it's already started.

Besides looking at processes using task manager, go over to the Performance tab and see what's happening with memory. The two points of interest are available physical memory and the peak commit charge (the limit is total RAM + total swap space). When the available physical memory gets low, Windows starts swapping memory to disk which is CPU and I/O intensive. When the peak commit charge is close to the limit, Windows has to work harder to find a place in the swap file for the data (make sure the swap file is about 1.5x the amount of memory - 1.9GB in your case).

Matt