OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Matthias Andree (madt.e-technik.uni-dortmund.de)
Date: Sat Dec 01 2001 - 17:22:17 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Andreas Hödle <Hoedlekwsoft.de> writes:

    > 1.) ext2 (CPU 70% Idle)
    > Client Ready : 0:58 min
    > 19 Msg./sec
    > Server Ready : 3:13 min (first smtpd -> last mail delivered according to
    > logfiles)

    Did you have /var/spool/postfix set to +S (check with lsattr) or mount
    it sync?

    > 2.) jfs (Ver. 1.0.5)
    >
    > Many errors.
    > Dead-Lock on <mailbox>.lck file
    > Corrupt files in postfix queue

    jfs 1.0.5 is not exactly current. Neither is Linux 2.4.10.

    > 4.) ext3
    > Client Ready : 4:16 min
    > 4,3 Msg./sec
    > Server Ready : 6:12 min (first smtpd -> last mail delivered according to
    > logfiles)

    Again, Linux 2.4.10 is not exactly current. If it was +S as per lsattr
    or mounted sync, updating to 2.4.16 may increase throughput. What
    journal mode did you use?

    > No tests about sync behavior or other advanced stuff.

    So the test does not reflect production setups?

    -- 
    Matthias Andree
    

    "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin - To unsubscribe, send mail to majordomopostfix.org with content (not subject): unsubscribe postfix-users