× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



-----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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.