如何提高postfix性能
如何使用TRAM提高你计算机的速度？英文的哦。不过太恐怖了。用ram。。[url]http://www.redwoodsoft.com/~dnelson/tram/tram.html[/url]
@_@~~
[wdb12][wdb12][wdb12]
以下是邮件列表的一个人说的话，确实是“化整为零”将负载分布到廉价的*nix box
================
寄件者：Craig Sanders ([email]cas@taz.net.au[/email])
主旨：Re: Making postfix faster?
View this article only
新闻群组：mailing.postfix.users
日期：2001-07-05 21:54:15 PST
On Thu, Jul 05, 2001 at 08:08:28PM -0400, Myke Olson wrote:
> Does anyone have any suggestions on making Postfix faster at sending mail?
> [...]
> We're running the latest version on a Sun Ultra1/140 and are only able
> to send about 160 emails/minute.
for this application, you may be better of with lots of cheap little
linux or freebsd boxes running postfix than one big Sun box.
one of the best ways is to have multiple cheap boxes rather than one big
expensive box.
this may require modifying your mailing list software so that it sends
part of each list to different machines. e.g. if you have 5 postfix smtp
sender boxes, then split the list in 5.
if you send individual messages to each subscriber rather than one message
bcc-ed to everyone then you could use a load balancer to spread the mail
load across multiple machine. e.g. linux virtual server (LVS) makes an
excellent load balancer - [url]http://www.linuxvirtualserver.org/[/url]
alternatively, use a large RAID array of as many disks as you can
afford. the more drives in the array, the better. e.g. if you want 72GB
of total space, it is much faster to have 8 x 9GB drives than 2 x 36GB,
or 4 x 18GB.
a solid-state disk (SSD) will be even faster than a raid array.
the way to scale up a disk I/O-bound application (such as sending to
enormous mailing lists) is to speed up the disk by adding more physical
disks and/or more machines or by using faster disks (e.g. SSDs).
combining the alternatives above will get even better results - e.g. an
array of 5 linux + postfix boxes, each with a 1GB SSD queue drive.
> Some ideas that I had were to somehow make it give up on the first
> try if the DNS record for a particular host didn't exist (i.e. a user
> signed up with [email]jdflkl@kjdjdflk.com[/email] as their email address) or somehow
> moving the spool directory into a RAM disk. But I couldn't figure out
> how to do that....
you could do that if you didn't care whether the messages got lost if
the system crashed or lost power.
a safer alternative is to use a non-volatile solid-state disk for the
postfix queue. in essence, they're a RAM disk with a battery backup
and a SCSI interface, in a standard disk form factor. they cost a
fortune, though, for any reasonable size....several thousand dollars per
gigabyte, last time i looked into them.
if 1 or 2 GB is enough for your postfix queue, then an SSD may be your
best option.
craig 第 5 条留言
寄件者：Len Conrad (LConrad@Go2France.com)
主旨：Re: Multiple frontend Postfix - One RAID5 storage
View this article only
新闻群组：mailing.postfix.users
日期：2003-01-14 06:47:20 PST
>mailserver-front--│
>mailserver-front--│--> store spool on 1 raid5 dev, seperate spools
>mailserver-front--│
It sounds like your are getting ready for very high volumes, so why have
you chosen the RAID that is slowest for writing? RAID1 has faster writing.
And of course going across a network to the spool dir is horribly slower
than local disk i/o.
RAID5 is fine for database work where read:write it 90:10, but mail is
closer to 50:50.
构筑高可靠的app，这个东西可以做个随时监测smtp 机器的mon。。不错不错。
[url]http://www.backhand.org/wackamole/[/url] 楼上鸟人该封号了。tmd
页:
[1]