Support Center > Search Results > SecureKnowledge Details
Testing Disk Drive Read/Write Speeds Technical Level
Solution

Use the below procedure and commands to get precise numbers on your disk drive performance.

These commands should work on any Gaia system starting from R80.10, regardless of hardware. They may also work on older software versions, but they have not been tested and may not be present.

Expected values can vary depending on what drives you have and how they are configured. For example, a system configured with RAID 10 will be faster than a RAID 5/6 system with the same number of drives.

  • Example values

    • 3.5" HDD - 80-160MB/s read/write speeds

    • 2.5" Sata SSD - 200-550MB/s read/write speeds

    • NVME SSD - 3000-7000MB/s read/write speeds

As long as your speeds do not differ significantly, your storage is likely to be functioning properly performance wise.

To get precise numbers on your disk performance:

  1. OPTIONAL: To make sure Check Point processes do not affect the performance on the disk and ensure the most accurate results, stop them:

    cpstop

    The rest of this procedure is safe to run during production, as it only consists of writing a 4GB file. However, processes that are running may lead to misleading numbers if they are writing to the disk. This is more of an issue on a Security Management server than on a Security Gateway.

  2. Find your disk drive designation:

    [Expert@HostName]# fdisk -l

    On a single disk system this will likely be /dev/sda

  3. Get your disk drive read speeds:

    [Expert@HostName]# hdparm -tv /dev/sda

    If your hdd designation is different, replace /dev/sda with the correct designation.

  4. Get your disk drive write speeds:

    [Expert@HostName]# dd if=/dev/zero of=/var/log/writefile oflag=direct bs=128k count=32k

    This command writes a 4GB file to test write speeds.

  5. Cleanup the write file so as to not consume disk space:

    [Expert@HostName]# rm /var/log/writefile

  6. If Check Point processes were stopped, restart them now:

    cpstart

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment