Stefan Foerster put forth on 1/23/2010 11:08 AM: > In case of severe server "overload", with postscreen(8) complaining > about lookup and update times around 400ms almost every mail, is it > (reasonably) safe as a last desperate measure to put $data_directory, > or at least the file referenced by $postscreen_cache_map, on a ramdisk > (e.g. "tmpfs" with Linux)? > > I know about RAM not being persistent across reboots, and I understand > what happens if the $postscreen_cache_map (or all the contents in > $data_directory) are lost.
If the problem is due to an I/O bottleneck, I'd recommend going SSD instead of RAM disk. Get this Crucial 64GB SATA2 unit and put both the postfix spool and postscreen db files on it: http://www.newegg.com/Product/Product.aspx?Item=N82E16820148318 Or, like Wietse said, first identify the actual cause of the problem. Then if it's I/O related, get an SSD drive. It's a relatively cheap path to massive random I/O throughput. -- Stan
