On Mon, 2006-02-20 at 14:04 -0600, Jan Depner wrote: > This is all well and good but you're only talking about CPU. Disk > I/O is another story entirely. If your WM starts doing some I/O that > you weren't aware of you may get an xrun because you couldn't access > the > disk in time. This is the reason that I kill syslogd before I record. > Granted, generally speaking you'll do OK due to the priority of your > process but disk I/O takes a certain amount of time and you can't > interrupt it once it's gone to the disk. > WM should do *very* little disk IO, and if disk access causes xruns, it means your recording app is VERY broken. If disk access delays the RT thread it should be using bigger buffers or something. If your WM is so bloated that it causes disk IO then the best advice is to get a better WM. Lee
