Re: [LAD] cpu spikes

2016-01-25 Thread Fokke de Jong
thanks for all your input, I’ll try and summarize here. > You're running Mint :-) Lots of background bells and whistles there, lots of > things which will crop up and interfere, things you cannot disable or turn > off with absolute certainty. If you want smooth power, you'll have to choose

Re: [LAD] cpu spikes

2016-01-25 Thread Len Ovens
On Mon, 25 Jan 2016, Joakim Hernberg wrote: I suppose hyperthreading could be a potential pitfall, but personally I see no problems with it with my audio workloads on my i7. hyperthread is only a problem with jack latency under 64/2... even on an older single core P4. (at least in my

Re: [LAD] cpu spikes

2016-01-25 Thread Len Ovens
On Mon, 25 Jan 2016, Len Ovens wrote: I am sure some will say that if rtirq doesn't help there is a bad driver... Check the actual priorities that rtirq sets. It seems to me the last time I checked that if an irq is shared by a, b an c and rtirq is used to prioritize c to 90 for example, a

Re: [LAD] cpu spikes

2016-01-25 Thread Len Ovens
On Mon, 25 Jan 2016, Fokke de Jong wrote:   16:          0          0          0          0   IO-APIC   16-fasteoi   madifx Is this your audio interface on irq 16? If so why is it sharing an IRQ? Move it to a different slot maybe? If this is a PCI card and there is only one slot, I would

Re: [LAD] cpu spikes

2016-01-25 Thread Len Ovens
On Mon, 25 Jan 2016, Jörn Nettingsmeier wrote: sorry to hijack this thread, but: when enquiring about latency tuning, one frequently encounters hints like "disable cron", "disable indexing services", "disable this, disable that". however, none of those alleged culprits run with real-time

Re: [LAD] cpu spikes

2016-01-25 Thread Tim Goetze
[Fokke de Jong] >I’m processing 32 sample-blocks at 48KHz but roughly every 0,6 >seconds I get a large spike in cpu usage. This cannot possibly be >explained by my algorithm, because the load should be pretty stable. > >I am measuring cpu load by getting the time with

Re: [LAD] cpu spikes

2016-01-25 Thread Joakim Hernberg
On Mon, 25 Jan 2016 12:53:57 +0100 Joakim Hernberg wrote: > On Mon, 25 Jan 2016 12:23:09 +0100 > Jörn Nettingsmeier wrote: > > > i understand how device drivers can be nasty (graphics cards locking > > up the pci bus, wifi chips hogging the

Re: [LAD] cpu spikes

2016-01-25 Thread Joakim Hernberg
On Mon, 25 Jan 2016 06:57:14 -0800 (PST) Len Ovens wrote: > On Mon, 25 Jan 2016, Joakim Hernberg wrote: > > > I suppose hyperthreading could be a potential pitfall, but > > personally I see no problems with it with my audio workloads on my > > i7. > > hyperthread is only

Re: [LAD] cpu spikes

2016-01-25 Thread Jörn Nettingsmeier
hi *! sorry to hijack this thread, but: when enquiring about latency tuning, one frequently encounters hints like "disable cron", "disable indexing services", "disable this, disable that". however, none of those alleged culprits run with real-time privileges or access driver or kernel code

Re: [LAD] cpu spikes

2016-01-25 Thread Joakim Hernberg
On Sun, 24 Jan 2016 15:03:08 +0100 Fokke de Jong wrote: > I am measuring cpu load by getting the time with > clock_gettime(CLOCK_MONOTONIC_RAW, timespec*) at the beginning and > end of each callback. When converted to a percentage my cpu load > hovers somewhere between 40

Re: [LAD] cpu spikes

2016-01-25 Thread Joakim Hernberg
On Mon, 25 Jan 2016 12:23:09 +0100 Jörn Nettingsmeier wrote: > i understand how device drivers can be nasty (graphics cards locking > up the pci bus, wifi chips hogging the kernel for milliseconds at a > time or worse...) but it seems that a) either kernel