Re: Poor raidframe reconstruct performance on 8-stable

[Mike Pumford <mpumford%mudcovered.org.uk@localhost>]

On 24/11/2018 09:19, Mike Pumford wrote:
> On 23/11/2018 22:20, Jaromir Dolecek wrote:
> > Can you perhaps try interrupt count via intrctl? iirc someone
> > complained about some interrupt storm coming from acpi.
> Didn't know about that one. That gives:
>
> interrupt id       CPU0  CPU1  CPU2  CPU3  device name(s)
> ioapic0 pin 9         0*    0     0     0  acpi SCI
> msi0 vec 0            0*    0     0     0  hdaudio0
> ioapic0 pin 16      432*    0     0     0  uhci0, unknown
> ioapic0 pin 21    76161*    0     0     0  uhci1, fwohci0
> ioapic0 pin 19 18004848*    0     0     0  uhci2, uhci4, ahcisata1
> ioapic0 pin 18        2*    0     0     0  ehci0, uhci5, ichsmb0
> msi1 vec 0            0*    0     0     0  hdaudio1
> ioapic0 pin 17       12*    0     0     0  unknown
> ioapic0 pin 23        0*    0     0     0  uhci3, ehci1, unknown
> ioapic0 pin 22   197505*    0     0     0  unknown, wm0
>
> pin 19 is the controller for the disks. and vmstat -i says:
>
> interrupt          total rate
> TLB shootdown     838374   16
> cpu0 timer       4919245   99
> ioapic0 pin 16       432    0
> ioapic0 pin 21     76219    1
> ioapic0 pin 19  18015996  364
> ioapic0 pin 18         2    0
> ioapic0 pin 17        12    0
> ioapic0 pin 22    197629    3
> Total           24047909  486
To follow up on this more this process isn't CPU limited in any way. The 
CPU time is reoproting as 99% idle consistently during the operation.



Mike