On a server, with less than 10 users, my server load stays at 1.00 all
the time. It seems that the qmlnxd is very heavy on the cpu. How can I
optimize that and avoid this server load ?
> On a server, with less than 10 users, my server load stays at 1.00 all
> the time. It seems that the qmlnxd is very heavy on the cpu. How can I
> optimize that and avoid this server load ?
I have responded off-list to Cedric on this problem. The qmlnxd process that is consuming all the processor power is looping trying to wait on a semaphore that doesn't belong to QM at all. We are investigating the possibility of a timing glitch that could cause a loop if QM is shutdown while qmlnxd is scanning for "lost" processes. So far, we have failed to find anything.
My recommendation to Cedric was to kill the looping process as is appears to be a remnant of a previous QM startup. We are still waiting confirmation from Cedric about whether this is a one off occurrence or a repeatable situation. This will help us diagnose the issue.
Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200
> I have responded off-list to Cedric on this problem. The qmlnxd process that > is consuming all the processor power is looping trying to wait on a > semaphore that doesn't belong to QM at all. We are investigating the > possibility of a timing glitch that could cause a loop if QM is shutdown > while qmlnxd is scanning for "lost" processes. So far, we have failed to > find anything.
That matches up with my memory of the CPU process hoggers I had. It was a while back, so memory is hazy. Restarting QM would not get rid of them, so a full reboot was needed.
We have identified the probable cause of this problem. The fix will be in release 2.9-10 though no date is set for this yet. If you need an urgent pre-build, please let me know.
Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200
> We have identified the probable cause of this problem. The fix will be in > release 2.9-10 though no date is set for this yet. If you need an urgent > pre-build, please let me know.
We can wait. I restarted QM at the beginning of this week and it seems fine now.