Paul Winkler wrote: > On Wed, Oct 06, 2004 at 12:01:43PM -0700, Mark Knecht wrote: > >>Hi all, >> OK, Last evening and this morning I have made good headway. It >>appears that the main culprit was ACPI support, or some part of it. >>With most of the ACPI stuff now disabled in the kernel build I am able >>to run jack with no clients attached, as a root or user with the lsm >>module modprobed, at p=8, n=2 for over 1 hour with no xruns. If my >>calculations are correct this would be a latency of less than 0.5mS! > > > p=8??? good lord. I'd like to see you try that with any real apps :-) > I'm happy if I can get 128, would like to get down to 64 reliably... > Well, it's not much of a test yet, but I've been running 24-bit drum loops in Ardour for the last 90 minutes from my internal hard drive at -p64, -n2. I can go to the console, change workspaces in fluxbox, do Evolution and have both Mozilla and Firefox open. No xruns. Using a consistent 16% of CPU and 170K-205K of disk bandwidth. It's very early yet. There is very little disk activity, but Ardour, Jack, and QJC seem happy so far. I'm sure this will come back and burn me in the next few hours. We'll see. I'm about to fire up jack_vst and Battery to see what happens there. - Mark
