Results 1 to 3 of 3

Thread: Hardware performance and Proxmox

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    Aug 2006

    Default Hardware performance and Proxmox

    The filtering process triggers quite a lot of database connections and several postfix connections. Therefore, the performance of the hard disk system is one very important parameter, especially fsyncs/sec. We introduced a small benchmark tool (proxperf) which you can run on the console (use it when the server is not under load).

    Here is a sample output (one cpu, single sata harddrive):
    proxmox:~# proxperf
    CPU BOGOMIPS: 4289.64
    REGEX/SECOND: 410814
    HD SIZE: 6.89 GB (/dev/sda2)
    BUFFERED READS: 116.38 MB/sec
    AVERAGE SEEK TIME: 8.09 ms
    FSYNCS/SECOND: 1084.51
    DNS EXT: 46.26 ms
    DNS INT: 1.05 ms (
    DNSBL: 35.47 ms (

    for actual hard drives, the result for FSYNCS/SECOND should be around 1000 or higher. Especially when you use hardware raid without write cache (and batteries backup), the performance concerning FSYNCS/SECOND could be quite bad (around 100) and the overall performance not as good as you expect.

    To get the best performance out of Proxmox:
    • Fast CPU, multi core cpu´s are recommended
    • Hardware raid controllers with batteries backup and write cache enabled and fast hard drives (Raid1, Raid5 or Raid10)
    • Fast DNS servers (maybe locally cached)
    Last edited by tom; 12-07-2007 at 12:52 PM. Reason: stick
    Best regards,

    Do you have already a Commercial Support Subscription? - If not, Buy now

  2. #2
    Join Date
    Oct 2007

    Thumbs up

    I can assertively confirm the importance of write cache enabled on the RAID systems. We have installed 2xProxmox 2.0 Anti Spam Gateways on HP DL380 G4 servers, with:
    1x3,0 GHz Xeon CPU,
    4 GByte RAM,
    3x72 GByte (15.000 RPM) SCSI HDDs,
    configured in RAID 5 with internal SmartArray 6i SCSI controller, without BBWC option kit (BBWC - battery backuped write cache). As result we can complain about realy bad I/O performance of the system:
    promox01:~# proxperf
    CPU BOGOMIPS: 12004.51
    REGEX/SECOND: 408455
    HD SIZE: 132.55 GB (/dev/cciss/c0d0p2)
    BUFFERED READS: 205.13 MB/sec
    AVERAGE SEEK TIME: 8.88 ms
    FSYNCS/SECOND: 123.90
    DNS EXT: 75.34 ms
    DNS INT: 2.31 ms (

    As comparison test we did install the same Proxmox configuration on my Windows XP workstation as VMWare appliance running under VMWare server 1.0.3 with 512 MB virtual RAM. The workstation is an HP PC, with 2,0 GHz Pentium4 CPU, 1 GByte RAM and 1xSATA HDD with 8 MByte cache(!!!). The performance (FSYNCS/SECOND) is much more better then on the high speed RAID configuration:
    FSYNCS/SECOND: 516.10

    Of course, after such blame comparison results we did order the BBWC option kit for both of our Proxmox mail gateways. I will report the new benchmarks results, after BBWC installation.

  3. #3
    Join Date
    Oct 2007

    Default Performance vlaue with BBWC installed

    As promissed, here is the new proxperf output, after we have installed the Battery Backuped Write Cache option on our servers:

    CPU BOGOMIPS: 12004.33
    REGEX/SECOND: 245574
    HD SIZE: 132.55 GB (/dev/cciss/c0d0p2)
    BUFFERED READS: 170.66 MB/sec
    AVERAGE SEEK TIME: 7.41 ms
    FSYNCS/SECOND: 1124.47
    DNS EXT: 376.00 ms
    DNS INT: 2.58 ms

    OK, the valur FSYNC/SECONDS varies, depending on current storage usage, because the server is running in production environment with over 120.000 mails/day.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts