4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Performance
FromSent OnAttachments
JuanEAug 8, 2000 8:11 pm 
Sam VarshavchikAug 9, 2000 9:02 am 
JuanEAug 9, 2000 4:08 pm 
Jason HaarAug 15, 2000 10:24 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] PerformanceActions...
From:JuanE (jua@ypay4it.com)
Date:Aug 9, 2000 4:08:12 pm
List:net.sourceforge.lists.courier-users

Sam Varshavchik writes:

JuanE writes:

I searched the archive and I saw nothing about this, but I am curious if anybody (Sam?) has any idea on how performance compares to that of Qmail. I'm just looking for ballpark figures.

It depends on your actual traffic pattern. Courier batches recipients for the same domain in a single transmission, and will reuse SMTP sessions, unlike Qmail. On the flip side, Courier usually rewrites most messages in order to add MIME headers. Also, Courier is a much larger mail server that Qmail, and requires more resources from the server.

What resources, I/O, RAM or CPU? CPU or RAM, I don't mind much (easy and relatively inexpensive), but I/O can be tricky.

How much larger, and what impact does that have on the resources? (My guess is that RAM usage will go up proportionately).

I think that Qmail will be faster than Courier for light mail traffic. I expect Courier to scale better as the mail load goes up. Batching recipients and reusing SMTP sessions also translates into considerably fewer DNS queries.

Let's not relive this thread :) Thanks, JES