need an upper thread cap
Bug #586141 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
loggerhead |
Triaged
|
Low
|
Unassigned | ||
loggerhead-breezy |
Triaged
|
Low
|
Unassigned |
Bug Description
when loggerhead gets busy, it keeps spawning new threads whenever there are lots of stuck ones. This is a problem because stuck threads still consume CPU and memory resources and exacerbate whatever problem is going on.
We should be able to say that there is a hard cap - say 20 - of threads, and that loggerhead never exceeds that. This would mean that if thread killing fails, we might stop servicing requests (but in that situation today we stop anyway). It would mean that when thread killing works, or busy threads eventually succeed, that service will be degraded not halted.
Bug 518689 has more discussion on the original report of this issue.
Changed in loggerhead-breezy: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
There is no current hard evidence that this would resolve (or even assist with) the problems that codebrowse experiences. Codebrowse has also been particularly stable recently.