2005/5/27, Will Dean <svn@indcomp.co.uk>:
> I think one of the difficulties is that the crawler is always going to
> generate a lot of disk access, and even if it does that in a super-clever
> fashion which means that it never interrupts anybody, people may STILL
> think 'disk access == computer busy' and wait for it to complete.
Problem is that the heavy disk access slows down other processes that
need to access the disk. You can try it: Put a working copy on a slow
(usb 1.1) memory stick, enable overlay icons on removable disks and
then try to work on that stick. It is basically unusable until the
cache has finished it's crawl. I know the overlay icons are not
recommended for removable drives, but you get similar results on slow
hard disks. The explorer is responding very poorly, but CPU load is
low. But I don't have an idea how to fix that...
I do not know in which order disk I/O requests are queued by the OS:
the order they've been requested, task priority or process priority
class? Maybe you could reduce the priority class of the cache process?
Something like
SetSetPriorityClass(GetCurrentProcess(), BELOW_NORMAL_PRIORITY_CLASS);
Norbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri May 27 10:15:33 2005