On Mon, May 25, 2009 at 01:38:41AM +0200, Eduard Bloch wrote:
> > I have noticed, that acng eats all available to a process
> > virtual memory after some days of work, and it starts
> > to return 503 to all requests.
> > It spawns a lot of threads and keeps them running.
>
> How many exactly? (ps
Thanks for quick answer.
I was not quite right about locking.
It still a race condition involving nSpareThreads, but more complicated.
When variable decrements, is supposed that some thread will be awaked,
but some other worker may return and take this job.
In this case number on spare threads nS
#include
* Alexander Inyukhin [Mon, May 25 2009, 01:30:38AM]:
> I have noticed, that acng eats all available to a process
> virtual memory after some days of work, and it starts
> to return 503 to all requests.
> It spawns a lot of threads and keeps them running.
How many exactly? (ps -L ...)
Wh
Package: apt-cacher-ng
Version: 0.3.11-1
Severity: normal
Hello
I have noticed, that acng eats all available to a process
virtual memory after some days of work, and it starts
to return 503 to all requests.
It spawns a lot of threads and keeps them running.
The reason of this behavior is race c
4 matches
Mail list logo
