Around about 26/01/11 14:43, Andy Levy typed ...
It's known and oft-lamented. NTFS just doesn't handle this scenario well - it's probably one of the reasons FSFS sharding was introduced (I'm speculating a bit here).
This is stuff that's currently in SourceSafe, which doesn't exhibit any obvious issues (well, apart from the obvious :) ), so I can't blame NTFS just for not handling the sheer volume of files.
How's the checkout performance with a command-line client on that XP box? It could also be your on-access virus scanner, and testing w/ the command-line client may help diagnose that.
I tested Linux command-line over a CIFS mount to the NTFS drive, on a box for which that directory was excluded for on-access scan, so the virus scanner isn't in the loop. Could be some other IT spyware^H^H^H^H^H^H logging software, though. But there's nothing using excess CPU in that case.
-- [neil@fnx ~]# rm -f .signature [neil@fnx ~]# ls -l .signature ls: .signature: No such file or directory [neil@fnx ~]# exit
