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



Rob Rogerson skrev den 12-07-2007 13:31:
I'm currently using WDSc 7.0 on a 2.66 GHz Pentium 4 with 1.74 GB of Ram.
Basic editing works okay but if I try other functionality (such as Outline
view refresh) the response is measured in minutes. I have been given the go
ahead to purchase additional hardware to make this more workable. My question is if by increasing only the Ram to 3GB will this be a vast
improvement? A colleague has a 3.0 GHz machine with 2.0 GB of Ram and his
response is acceptable. My thought is that WDSc is processor intensive and
the CPU speed definitely makes a difference. I don't want to purchase
additional Ram when the CPU really should be faster.
Eclipse generally prefers memory to cpu-power.

Try looking at the task manager to see if it is the CPU or the memory that is the bottleneck, by
seeing if it is the cpu usage that goes to 100% (divided by number of cores in your system) or if the process page swaps a lot. You may want to see additional columns in the process view.

My guess is that your money is spent the best by filling up your machine with memory.

Please also note that if you do other stuff, Windows XP notices that WSDCi is not in the foreground and rolls out the process to disk causing sluggish performance. If this bites you, there is a trick available as a plugin IIRC.

Good luck, I am generally satisified with WSDCi and myeclipse running at the same time.


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.