Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Victor Duchovni (Victor.Duchovnimorganstanley.com)
Date: Mon Mar 23 2009 - 18:16:34 CDT
On Mon, Mar 23, 2009 at 06:15:13PM -0400, Brandon Hilkert wrote:
>> MEASURE! Find out what is slowing it down. When you know what that
>> is, ask the question again.
> What are the best tools to get a feel for hardware performance and
> utilitization? Top, atop, vmstat ?
> As you can probably tell, I don't have much experience working with Linux.
> If you feel like this is a question not worth the time, then don't feel
> like you have to respond.
It is a difficult question. The tools in hand are strace, iostat, top,
mpstat, ... You can also add a CPU-intensive task in the background and
see whether this impacts DKIM throughput. You could add a disk intensive
task and see how that impacts throughput... You could switch to tmpfs
for everything, increase concurrency (won't help with CPU but can ammortize
latency). Is the DKIM filter doing DNS lookups? If so you could have a latency
problem, without exhausting any local resources...
Identifying bottlenecks is hard work. Good luck. Your Postfix can go fast,
now you just need to configure DKIM to not get in the way. This should
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.