|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Vivek Khera (khera
kcilink.com)Date: Fri Sep 28 2001 - 09:17:48 CDT
>>>>> "CP" == Chip Paswater <turk182
chipware.net> writes:
CP> You're talking about a kernel RAMDISK and not one of those solid state
CP> ramdrives? Performance wise, how do they compare to each other? I'm
CP> assuming the ramdisk is the fastest because you're not going through an IDE
CP> bus to get the data...?
The SSDs that I use work over a SCSI bus. They are obviously not as
fast as local RAM, but then that's expected. They do however provide
you with assurance of not losing your data upon crash or accidental
pulling of the plug or something. And don't say "my systems never
crash". Sooner or later, one will.
CP> And I assume postfix can handle multiple queue directories? I
CP> wouldn't mind having a 256M ramdisk for everyday queues, and then
CP> a larger 2-3 gig queue for the days when I lose a T3 or two. Can
No, but you can have mulitple instances of Postfix. The first one
which uses the RAM disk spool, since it is expensive, uses the second
one as a fallback_relay. Then any initial attempts to deliver that
fail will be handed over to the second one which uses your big slow
disk to hold the mail. The two instances of postfix can either be on
different machines, different IPs on the same machine, or different
port numbers on the same machine.
CP> I preferentiate the ramdisk over the hardisk, so that postfix
CP> won't start using the harddisk until the 256M ramdisk is full?
Not that I am aware of. Postfix pretty much expects its spool
structure to be one file system.
-
To unsubscribe, send mail to majordomo
postfix.org with content
(not subject): unsubscribe postfix-users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]