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.
On Tue, 22 Oct 2002 13:28:44 +0200, Anders Truelsen wrote: > Updates on the other hand really pull the teeth out. > - A single update of a large workspace pushes the CPU to 100% for up to > 30 seconds. > Why is that? - I never observed that behavior on the old machine. Update is a two-step operation. In the simplest case the names & datestamps of the files in each client directory are sent and the server then decides what (if anything) to send to a client. If the client thinks something has changed on its side it sends the suspect file for diff/collision detection, which is stored temporarily on the server. This can use up a fair bit of temporary drive space in the worst case (such as all files appearing modified). It shouldn't affect CPU much though. I'd check that your IDE interface has DMA enabled - if it's on PIO it'll be using up all the CPU accessing the disk. Tony