innfeed as a memory eating hog - crazy hog!
Andrew A. Vasilyev
andy at demos.su
Fri Mar 16 21:18:44 UTC 2001
> I'll bet you're using CNFS. innfeed will have a bunch of sections
> of your CNFS buffers mmap'd. Those mmap'ed regions are in the
> process' address space which is why the size looks so huge (I see
> the same thing with HP/UX). But notice that your RES is a much more
> reasonable size. That's how much RAM is actually used by that
Unfortunately this is not so good as you describe :((
I know about mmap, but the following figures are not due to
this call, but all the memory had been eaten by malloc()-s,
and was visible as heap, not system shared memory. Please pay
attention to free memory below - and the system has 1GB RAM,
and now - without leaking innfeed, - we have 600MB free.
I can say the same about swap - we have 1GB free space there,
but today morning 2/3 was used. So the problem is still exists,
I saw this pig not for the first time. :((( Is there any chance
of Pyrify-ing this monster?
> > Hi!
> > Does anyone have the same problem, or this is a local glitch?
> >Memory: 1024M real, 17M free, 940M swap in use, 329M swap free
> > PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
> >11763 news 1 60 0 827M 36M sleep 22:46 2.27% innfeed
> > ^^^^^^
> > I have only one (1) peer at this instance of innfeed,
> >max-queue-size: 25
> >max-connections: 12
> > local peer, connected via Fast Ethernet. innfeed from INN 2.4.0
> > (20010315 CVS prerelease).
> > ANDY
More information about the inn-workers