On Oct 6, 2007, at 5:50 AM, Rob Mueller wrote: > If it wasn't IO limit related, and it wasn't CPU limit related, > then there > must be some other single resource that things were contending for. > > My only guess then is it's some global kernel lock or the like. > > When the load skyrocketed, it must have shown that lots of > processes were > not in S (sleep) state. Were they in R (run) state or D (io wait) > state? > Since you're on Solaris, you could use DTrace to find out what they > were > actually doing/waiting for... The lockstat command is where one would enter this territory. lockstat -D 20 sleep 5 Will show you the top 20 contended locks. lockstat -kgIW sleep 5 Will show you what calls are taking them most time to complete in the kernel during a 5 second sample period. /dale -- Dale Ghent Specialist, Storage and UNIX Systems UMBC - Office of Information Technology ECS 201 - x51705 ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
