Unknown Sender wrote:
Hi, I'm having some performance issues lately.
For those people managing big ISP's qpsmtpd's, how
is your general configuration?
What server version are you using?
qpsmtpd
qpsmtpd-forkserver
qpsmtpd-prefork
qpsmtpd-server
0.3x? or another svn branch? (or some private version of qp?)
I've read somewhere Ask is having 2000+ concurrent connections
in apache.org (or was it in perl.org?)
Is that true? 2000+ forked process in forkserver seems too much
are you using prefork? or qpsmtp-server (nonblocking)?
The Apache.org and perl.(com|org) servers are probably the hardest hit;
I'll let them answer if they want. I can say that the 2000+ concurrent
connections was mentioned in reference to the current trunk code (which
is a using completely different dispatch method) being used primarily in
a spamtrap enviroment. Matt Sergeant is the one to talk to here, but
the last word was there were mysterious lost messages with the trunk
code that he was unable (ENOTIME) to track down.
Honestly, you are better off running multiple equal-distance MX boxes
(i.e. all 0) in parallel, rather than trying to maximize your
performance on one or two boxes. I suspect with the free VMWare Server
software, you could run 4 qpsmtpd instances very comfortably on a single
3GHZ 1U rack server with 2GB of ram. I say that because our primary MX
boxes are more like 400MHz MIPS clones with 512MB, and load hardly ever
gets above 1 (even with two independent antivirus scanners). Of course
I'm not an ISP and I max out around 15 simultaneous connections.
John
