Guys,
We're now quite consistently hitting MAX_CHILDREN limit of 300 in pop3 during
business hours. I understand it's hard set in code to 300 (after pushing it
higher and getting warnings in logs I checked through the code).
What are the implications of increasing this limit?
Regards
Jon
On Dienstag 16 Juni 2009 Jon Duggan wrote:
MAX_CHILDREN limit of 300 in pop3
Are you sure your box has enough RAM to keep 300 pop3 daemons around,
plus the memory they need during I/O? Maybe it'd be better to install a
2nd box? If your machine is already swapping, more processes with
actually
The hardcoded ceiling was aimed at avoiding overloading the database
server. You can change the value and recompile if you like.
It does make me curious what hardware are you on anyway?
Wish I had a good load tester for pop3...
Michael Monnerie wrote:
On Dienstag 16 Juni 2009 Jon Duggan
The pop3 box is a dedicated quad core with 4gb of ram.
I've watched the box looking for bottlenecks during the busy periods, there are
no bandwidth/cpu/disk bottlenecks on the pop3 server, likewise ive watched the
backend server which seems like it's at reasonable load but not exhausted as
far
Thanks Paul, I'll up to 450 and see how we go.
Our pop3 box is a quad xeon with 4gb of ram, the DB backend is a dual quad xeon
with 16gb of ram using mysql.
Which leads me to another question. It seems for good reason that people
running larger setups are preferring postgres, is there
On Dienstag 16 Juni 2009 Jon Duggan wrote:
The pop3 box is a dedicated quad core with 4gb of ram.
And how much memory is used during peak hours? Just curious. Each
dbmail-pop3 daemon here is shown as having an RSS footprint of 1-2MB,
and a VSZ of 5-10MB. So with 300 users you'd have about 13MB
