|
> So when that's happening, is it slamming the CPU, disk, or network? > Properly isolated, it may be solveable. Processor. But not to maximum utilization. I'm not in the vicinity of my dual-core machine right now, so I just tested on a 2.8Ghz P4 with 1.5GB of RAM. My test was a simple cut/paste of about a dozen source lines. It runs the processor up to 70% for 2-3 seconds (duration of the paste operation), then falls back to idling at around 10%. Disk and memory are not affected in any measurable amount. Any operation which requires the insert of one or more new lines in a source member exhibits this performance problem, otherwise it runs well. > BTW, a side note about the RAM, if Joe does the VMWare thing > as I suggested he may want >2GB to handle the VMs he'll be > running. It'll depend on the number and nature of the VMs he > sets up. Here, we're buying about 1GB RAM per VM. Good point. I run VMWare as well, and the additional memory makes a big difference for VM's. John Taylor
As an Amazon Associate we earn from qualifying purchases.
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.