SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Dell Technologies Inc. -- Ignore unavailable to you. Want to Upgrade?


To: Walt Corey who wrote (45070)5/27/1998 5:05:00 PM
From: MichaelW  Read Replies (1) | Respond to of 176387
 
I've been using a 200mhz for a while. Now I think it's slow.

Are you going say to me that people don't like power?




To: Walt Corey who wrote (45070)5/30/1998 1:22:00 PM
From: rudedog  Respond to of 176387
 
Walt -
If NT is beginning to thrash you probably need more RAM, not a faster CPU. Run performance monitor and watch CPU utilization, and memory page faults per second. I would bet that your CPU utilization is below 50% on average even with a 133 but that your page fault rate is bumping up into the 100+ range. If average page faults per second get above 70 you are going to be disk bound. a faster disk can help (by allowing more page faults) or a disk array (which I use) can allow a much higher rate (300-400) before the bottleneck gets severe. But the easiest solution is just add more RAM and the page fault rate will drop.

Looking at available bytes (memory) can also be a good clue, NT should maintain the available pool at about 4MB, if it gets lower than that, the memory manangement system invokes the background task that tries to free up least used pages by faulting them to disk. This will use up both CPU and disk, but it is really a memory problem.

It is easy on NT to see what benefits you can get from a faster CPU vs more memory vs a faster disk. Most people find that a faster CPU is the least of their problems (although it can mask the problem).