Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Hello All,
IDS 11.50.FC8W2 on HP-Unix
We experinced some dip in our performance(load jobs) and while checking the
user I saw quite many sessions with S- flag indicating these were waiting on
mutex.
I checked in onstat -g ath and found the following different waits:
8815514 c000000a2ee36030 c000000a8fa7db48 1 mutex wait pt_940000a 12cpu sqlexec
9376796 c000000a54e18c10 c000000a865a1550 1 mutex wait nsf.lock 11cpu* sqlexec
9331804 c000000a2e8c1720 c000000a7ddc4888 1 mutex wait hash 0 175 10cpu sqlexec
8660524 c000000a3511a030 c000000a7ddf58d8 1 mutex wait <unknown> 9cpu sqlexec
8897413 c000000a511d3ae0 c000000a3777d370 1 mutex wait netnorm 1cpu sqlexec
8660524 c000000a3511a030 c000000a7ddf58d8 1 mutex wait hash 0 286 5cpu sqlexec
Not all of these are waiting for nsf.lock! and I dont know what the others
mean(hash 0 175, pt_940000a) ?
Drilling down from ath - users - ses I saw the SQLs waiting for mutex, however
these are normal SQLs running almost all the time while loading jobs run.
What more do I check to link the performance dip with the mutex waits?
Regards,
Vikas
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.