On Thu, 2 Jun 2005, Torsten Landschoff wrote:
Hi Ulrich, [...] That's unlikely to happen. And, BTW: I guess this bug is also a problem with the current linux kernel. Somebody on linux-kernel pointed out that he got 10% CPU usage by having 3 processes talk to each other in a ring inside an endless loop. For some reason the scheduler thinks that no process is ready to run.
Hmm, possibly there is a problem with the scheduler itself. However, as I have written, the problem didn't show up with woody and a 2.6.7 kernel. I have applied the tag "sarge" because of this - why was it removed?
I noticed that in all operating system configurations where the problem arises (that is, when using sarge), the slapd fails to spawn additional threads when a query is made (which it does when using woody). Maybe here something is wrong?
What does top say about your CPU usage?
I don't see anything conspicuous - if I start a CPU consuming process, it gets 99%, and slapd almost doesn't show up.
Talking about severities: We will not delay sarge because slapd has a performance problem for one user.
I am respecting your decision, of course, and I understand completely that time is short now.
However, though I have not tested everything, the bug really doesn't seem to be specific to any aspect of our slapd configuration, which is simple and standard. (Please tell me if I you think that the problem doesn't arise in every slapd configuration.) And it is not just a performance problem - as I have written, the slapd needs more than 2000 x the amount of time it would need without a concurrent process. For all practical purposes: It just hangs. I didn't exaggerate to make it seem more important. Don't just believe me: This can be reproduced very easily.
Best regards Ulrich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
