innfeed bloats and explode
rra at stanford.edu
Tue Feb 4 19:04:03 UTC 2003
Alex Kiernan <alexk at demon.net> writes:
> "Marco d'Itri" <md at Linux.IT> writes:
>> It's 25 and peers*25*1MB does not account for 1.3 GB.
> I /think/ from a quick read of the source max-queue-size is
> per-connection, so you have peers * max-queue-size * max-connections *
I've seen people report this from time to time. I shunt binaries to a
separate innfeed and throttle its max-queue-size and I've never seen this
problem. This makes me think that's the underlying cause (although of
course I can't rule out a memory leak in innfeed itself).
Should we lower the default max-queue-size on the grounds of choosing
safety over some speed?
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
More information about the inn-workers