Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
> From: Stéphane Nicoll [mailto:Stephane.Nicoll at bsb.com] > I've made more tests today using the "Performance" tool > available on Windows 2000 server. The %disk time and %disk > write time is almost 100%, the %idle time is almost 0% !! That sounds like an issue, certainly. I'd suggest measuring the average disk queue length rather than the %time, however. There are two things to check here: memory usage and disk I/O. Too little RAM can cause heavy disk traffic due to paging, or you might have plenty of memory but CVS is simply hammering the disk. Try monitoring Memory / Pages Output per second and Memory / Available memory (you can get a quick idea of the latter by looking at Task Manager). Windows NT/2000/2003 will try to maintain around 10% of physical memory as available memory. If your available memory is much lower than that, something's almost certainly causing memory pressure. This could be file cache or process memory; Pages Output should help you to tell the difference. If Available Bytes is OK and there's not too many Pages Output, you've probably saturated your disk I/O. What's the disk subsystem? - Peter