Nice, this is definitely pointing the finger more definitively. Next
time could you try:
dtrace -n '[EMAIL PROTECTED](20)] = count()}' -c 'sleep 5'
(just send the last 10 or so stack traces)
In the mean time I'll talk with our SPA experts and see if I can figure
out how to fix
Hi.
Today again the same problem - however not that severe so I'm not sure if
below lockstat is representative.
# lockstat -kgIW sleep 5 | less
Profiling interrupt: 1968 events in 5.072 seconds (388 events/sec)
Count genr cuml rcnt nsec Hottest CPU+PILCaller
