Is the decision to keep data in memory as opposed to some sort of database a speed issue? It seems that there would be a lot of benefit to keeping the active data in an sql database accessible from other apps. Oliver Fromme wrote: > > > Petar Bogdanovic wrote: > > I just did some stress-testing on milter-greylist in order to test its > > memory consumption and it seems that there are some leaks to be found. > > milter-greylist keeps all data (all triples) in memory. > So it is expected that it will grow if new triples come > in faster than old triples are expired, which was certainly > the case in your 30-minutes test when the timeout was set > to 1d. > > Best regards > Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Gesch\ufffdftsfuehrung: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn- > chen, HRB 125758, Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart > > FreeBSD-Dienstleistungen, -Produkte und mehr: > http://www.secnetix.de/bsd <http://www.secnetix.de/bsd> > > "To this day, many C programmers believe that 'strong typing' > just means pounding extra hard on the keyboard." > -- Peter van der Linden > >
Message
Re: [milter-greylist] memory consumption
2008-10-22 by Mark Walker
Attachments
- No local attachments were found for this message.