Thanks for retesting. In hindsight my analysis has a fatal flaw. I used the
reap deficit at the end of the run of 162468 threads to estimate hash table
residency, but the residency should instead track the steady state rate of
thread creation/destruction of approx 5000 threads (assuming that t
Right - there's no reason to guess here;
#dtrace -n 'syscall:::entry { @[execname,probefunc] = count() }'
Control c after 10-30 seconds or or.
You'll get a sorted list of process names and which system
calls they're calling.
Change "execname" to "pid" or PIDs are more usefull,
or use both
Hi Matt,
why "suppose" who is making the syscalls when you can know ?
run prstat -mL and check it SCL rate
or truss -c the process.
HTH
Paul
>- Begin Included Message -<
Date: Fri, 23 Oct 2009 00:06:31 -0700 (PDT)
From: "Matt V."
Subject: Re: [perf-discuss] Kernel usage
To: perf-dis
Thanks for your response.
For moment, we can't patch Oracle version (production environment).
But on another server (which contains containers too), we have the same problem:
> sar 1 100
SunOS 5.10 Generic_137137-09 sun4u10/23/2009
09:00:17%usr%sys%wio %idle
09:00:18 12
