Hello, We had a situation on a t5140 running solaris 10 where the load average from prstat were 20-25,30-40,60-80. We ran a simple dtrace cmd to capture the jstack using the pid provider using the PID from prstat. That action pushed the 1 minute load average to 120. Not only that we were not able to get any o/p, the system became unresponsive to SSH sessions. Ctrl-C were ignored for atleast 30 seconds. Some other simple dtrace one liners to aggregate syscalls per PID also resulted in the same behaviour. Any dtrace action during that time pushed the load significantly. I would like to believe that is an case operator error than dtrace issue. Please let us know if we missed something or if there are tunables in those situations.
dtrace cmd used dtrace -n 'pid1234:::ent...@[jstack()] = count()}' and some other simple dtrace one liners to aggegate syscalls/pid. Thanks -- This message posted from opensolaris.org _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
