> Hey, my comments were made as someone who uses a 15K boot 
> disk on his home PC.  Yeah, it is a ton faster (my wife's PC 
> had a 10K SCSI disk).
> The question, though, is how important is disk performance 
> after things load up?  WDSC, WAS, Java, etc. are RAM pigs; 
> more RAM may be a better choice than the more expensive disk.

There seems to be a point where WDSc simply doesn't benefit from more RAM;
which would be great if that mean't it was running fast. Unfortunately, it
doesn't. About 2 months ago, I went from a 800Mhz P3 with 768MB of RAM and
5400rpm IDE drive, to a dual-core Athlon XP with 2GB of RAM and a 10Krpm
SATA drive. 

With the new machine, the intial load time for WDSc is much better, as one
would expect. Running a Verify and refreshing the Outline view are also much
faster (as long as you're using a local cache). However, the RSE editor
itself still bogs down badly when doing cut/paste operations, or inserting
lines. When I check my memory utilization, it's nowhere near what I have
available.

I recall reading that WDSc defaults to using up to a maximum of 1/3 of
available memory. My experience is that it doesn't even reach that before
beginning to exhibit sluggishness. And when I say sluggish, I'm talking
about 2 seconds to insert a line kind of sluggish. Just brutal. Turning off
the "Automatic syntax checking" in the LPEX preferences improves things
considerably, so the problem seems to be localized to the IBM customized
editor. The overall workbench, views, perspectives etc., run quite well. 


John Taylor


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.