Le jeu 13/10/2005 à 09:12, Fredrik Nyberg DC a écrit : > Matt Kettler wrote: > > Based on that you're talking about 50 million entries. If you've got a 5-day > > timeout that's only 10 million attempts per day. For a site with 8,000 users > > that doesn't seem unreasonable. > > We have around 1 million entries in our greylist database. What really > bugs me is that the current 2.3 GB of VmData that milter-greylist is > using does not show up in physical memory or swap... it will be > interresting to see what happens when the process hits 3 GB, since this > is the amount of memory + swap that one of the servers has. > > Could perhaps the kernel (Linux 2.6.9-11.ELsmp, CentOS 4.1) be reporting > the memory usage wrong? This problem seems to have started since I began > using the mxsync function. > > Time for me to "Use the Source, Luke". > > Cheers, > Fredrik Nyberg Storing the md5 of the tuple instead of the tuple itself could be a solution for a large site and an a new option for milter-greylist. md5 is only 16 byte long (against ~ 64) md5(Sender IP:Sender e-mail:Recipient e-mail) Time -- Christian Pélissier Office National d'Études et de Recherches Aérospatiales BP 72 92322 Chatillon Tel: 33 1 46 73 44 19, Fax: 33 1 46 73 41 50
Message
Re: [milter-greylist] milter-greylist using large amounts of virtual memory
2005-10-13 by Christian PELISSIER
Attachments
- No local attachments were found for this message.