> Ok, for system cpu time usage:  try to run a kernel
> profile, to find out what kernel functions are
> consuming
> the time,  lockstat -kIW -D 20 sleep 15

I did one on the machine, and then quickly an ssh and another one in ssh for 
the screenshot:

# lockstat -kIW -D 20 sleep 15

Profiling interrupt: 3074 events in 15.841 seconds (194 events/sec)

Count indv cuml rcnt     nsec Hottest CPU+PIL        Caller                  
-------------------------------------------------------------------------------
 2430  79%  79% 0.00     2682 cpu[0]                 i86_mwait               
  279   9%  88% 0.00     1364 cpu[0]+4               tsc_read                
  113   4%  92% 0.00   554980 cpu[0]+4               ddi_mem_get32           
  103   3%  95% 0.00     1437 cpu[0]+4               tsc_gethrtime           
   53   2%  97% 0.00     1369 cpu[0]+4               mul32                   
   35   1%  98% 0.00     1337 cpu[0]+4               gethrtime               
   28   1%  99% 0.00     1379 cpu[0]+4               drv_usecwait            
   11   0%  99% 0.00     4931 cpu[0]                 (usermode)              
    4   0%  99% 0.00     2269 cpu[0]+4               do_splx                 
    2   0%  99% 0.00     2306 cpu[1]                 fsflush_do_pages        
    2   0% 100% 0.00   279710 cpu[0]                 ddi_io_getw             
    1   0% 100% 0.00     2382 cpu[1]                 as_fault                
    1   0% 100% 0.00     1887 cpu[1]                 xsetitimer              
    1   0% 100% 0.00    13510 cpu[1]                 segvn_lockop            
    1   0% 100% 0.00     1705 cpu[0]                 poll_common             
    1   0% 100% 0.00     4468 cpu[1]                 syscall_mstate          
    1   0% 100% 0.00     3378 cpu[1]+11              thread_lock             
    1   0% 100% 0.00     2526 cpu[1]                 page_trylock            
    1   0% 100% 0.00     2103 cpu[1]                 kstat_compare_bykid     
    1   0% 100% 0.00     1403 cpu[1]+9               mutex_delay_default     
-------------------------------------------------------------------------------

and 10 seconds later it was completely dead.

Does this help, or do you need another one?
-- 
This message posted from opensolaris.org

Reply via email to