Re: Re: [opm] memory leak?
ongeboren <[email protected]>
| Newsgroups | gmane.network.irc.bopm |
|---|---|
| Message-ID | <[email protected]> |
Hi again, I moved forward to make tests and put the bot to work with negcache set to 600 seconds. In 48 hours the bot was using ~250MB. Tests without negcache were using too much resources and I didn't do them for long time. The FDs jumped quite high and the bot was still adding quite a lot of KB to it's memory every minute. In the evening when the network had ~30K users, after 90 minutes of working without negcache the bot had scanned 41584 connections and was using 81MB of memory. Is this still normal? I would really like to limit the memory the bot uses so I don't have to restart it every 48 hours when it had used most of the free memory of the system. I did also some tests with valgrind. It didn't report anything. I did the tests with valgrind using negcache and without it. Further, I suppose the many MBs in memory are not linked to the caching of non-proxy hosts. All I know is that there is definitely something wrong. Let me know if there is anything I can do further in order to solve this issue. Regards, ongeboren --- ongeboren <[email protected]> wrote: > OK, lets switch to the other list list. > > For information: > the box is a debian linux, bopm version is 3.1.2 > (compiled from > sources from blitzed.org). > > > On Thu, 30 Dec 2004 19:48:11 +0000, Andy Smith > <[email protected]> wrote: > > On Thu, Dec 30, 2004 at 08:34:32PM +0100, > ongeboren wrote: > > > Hello, > > > > > > I am trying to understand why a bopm bot reaches > more than 600MB in > > > the memory in a 3 days time span. > > > > I don't know the answers here really, but this is > the wrong list; > > you want the bopm list. > > > > > The bot was intentionally under > > > heavy load and about after the 1M connection he > has used most of the > > > free memory of the mashine it was running on, > what forced a manual > > > restart. > > > > I do know that if you add so many ports that the > scanner can't keep > > up with the rate of connecting users then the scan > queue will grow > > without limit. But that may not be the problem. > > > > > I suppose it is important to mention that the > negcache variable is set > > > to 4 hours. > > > > Have you tried it without this? > > > > > > > > > -- > One only sees what he wants to see in other people. > Problems start when one sees what he doesn't want to > see. > __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250