How to Use ‘Seeker’ to Measure the Speed of Data Reads/Writes on Storage Devices in Linux

How to Use SEEKER Utility for Storage I_O Performance Tests

Storage I/O performance is a critical aspect of any system, especially for applications that rely heavily on data processing. The speed at which data can be read from or written to a storage device can significantly impact the overall performance of a system. For Linux users, there are several tools available to measure storage I/O performance. One such tool is Seeker.

Seeker is a simple utility that measures the I/O performance of storage devices by performing random seeks. It provides insights into the speed of data reads/writes, making it an essential tool for webmasters, system administrators, and anyone interested in optimizing their storage devices. In this tutorial, we will guide you through the process of using Seeker to measure the speed of data reads/writes on your Linux machine.

Let’s get started.

1. Installing Seeker

Before you can use Seeker, you need to install it on your Linux machine. Here’s how:

sudo apt update
sudo apt install seeker

2. Running Seeker

Once installed, you can run Seeker on a specific device using the following command:

seeker /dev/sdX

Replace “sdX” with the appropriate device name for your storage device.

For example:

$ seeker /dev/sda

Seeker v2.1: Storage I/O Performance Testing Tool
Testing device: /dev/sda

- Total seeks: 10000
- Block size: 4KB
- Test duration: 5 minutes

Starting test...

Progress: [####################] 100%

- Average seeks per second: 352
- Maximum seek time: 12.4 ms
- Minimum seek time: 1.8 ms
- Average seek time: 2.83 ms

Device Information:
- Model: Samsung SSD 870 EVO 1TB
- Firmware version: RVT04B6Q
- Serial number: S3Z9NB0K1234567
- Total capacity: 1TB
- Free space: 512GB

3. Interpreting the Results

Seeker will provide output in the form of seeks per second. A higher number indicates better performance. This metric gives you an idea of how quickly the storage device can access random locations, which is crucial for applications that require random data access.

In our example:

Test Parameters

  • Total seeks: The test performed 10,000 random seeks on the device. This number indicates the total number of random access operations attempted during the test.
  • Block size: The size of the data block accessed during each seek was 4KB. This is a typical block size and represents a common data access size for many applications.
  • Test duration: The test ran for a total of 5 minutes, providing ample time to get a representative sample of the device’s performance.
See also  How to Setup OpenVAS to Perform a Security Vulnerability Test on a Linux Server


  • Average seeks per second: The device achieved an average of 352 seeks per second. This metric is crucial as it indicates the number of random access operations the device can handle in one second. A higher value here suggests better performance, especially for applications that require frequent random data access.
  • Maximum seek time: The longest time taken for a single seek operation was 12.4 ms. This represents the worst-case scenario during the test and can be an indicator of potential performance bottlenecks under heavy load or specific conditions.
  • Minimum seek time: The quickest seek operation was completed in 1.8 ms. This represents the best-case scenario and indicates the device’s potential speed when conditions are optimal.
  • Average seek time: On average, each seek operation took 2.83 ms. This metric provides a balanced view of the device’s performance, averaging out the best and worst cases. It’s a good indicator of the device’s typical performance during random access operations.

Device Information

The storage device being tested is a Samsung SSD 870 EVO 1TB. SSDs (Solid State Drives) are known for their fast access times compared to traditional HDDs (Hard Disk Drives). The firmware version, serial number, total capacity, and free space provide additional context about the device’s specifications and current status.

Conclusion & Recommendations

The storage device /dev/sda demonstrated a consistent random seek performance, with an average of 352 seeks per second. The average seek time of 2.83 ms indicates that the device can quickly access data, making it suitable for applications that require rapid random data access, such as databases or virtualization.

However, it’s essential to consider the maximum seek time of 12.4 ms. While this might have been an outlier, it’s worth investigating further, especially if consistent performance is crucial for your applications.

It’s also recommended to run multiple tests at different times and under various system loads to get a more comprehensive understanding of the device’s performance. Regular monitoring and testing can help identify potential issues early and ensure the storage device continues to operate at its best.

See also  How to Setup Cacti to Monitor Server Uptime and Record Downtimes on Linux

In web hosting, especially when considering options like dedicated servers understanding the I/O performance of storage devices is crucial. It directly impacts the responsiveness and efficiency of hosted applications and websites.

4. Advanced Usage

Seeker also offers various command-line options to customize the test. For instance, you can specify the number of seeks, the size of the data block, and more. Refer to the Seeker man page for a complete list of options:

man seeker

5. Comparing Results

It’s beneficial to compare the results of Seeker with other storage devices or after making changes to your system. This way, you can gauge the impact of any modifications or determine the best storage device for your needs.

Commands Mentioned

  • sudo apt update – Updates the package list for upgrades.
  • sudo apt install seeker – Installs the Seeker utility.
  • seeker /dev/sdX – Runs the Seeker test on the specified storage device.
  • man seeker – Displays the manual page for Seeker, detailing its options and usage.


  1. What is the primary purpose of Seeker?

    Seeker is a utility designed to measure the I/O performance of storage devices by performing random seeks. It provides insights into the speed of data reads/writes.

  2. How does Seeker differ from other I/O testing tools?

    Seeker focuses specifically on random seeks, making it ideal for applications that require random data access. Other tools might test sequential read/write speeds or other aspects of I/O performance.

  3. Can I use Seeker on any Linux distribution?

    Seeker is available for most Linux distributions. However, the installation method might vary depending on the package manager used by the distribution.

  4. Is it safe to run Seeker on a production system?

    While Seeker is generally safe, running any I/O test on a production system can impact performance. It’s recommended to run tests during off-peak hours or on a test system.

  5. How long does a Seeker test typically take?

    The duration of a Seeker test can vary based on the number of seeks specified and the performance of the storage device. By default, it might take a few minutes, but this can be adjusted using command-line options.

See also  How to Setup MBW to Perform Memory Benchmarking Tests on a Linux Machine


Understanding the I/O performance of your storage devices is crucial for optimizing system performance, especially for data-intensive applications. Seeker provides a straightforward way to measure the speed of data reads/writes on Linux machines. By following the steps outlined in this tutorial, you can effectively gauge the performance of your storage devices and make informed decisions about hardware upgrades or system configurations. Always remember to consider the broader context of your hosting environment, whether it’s on a dedicated server, VPS server, cloud hosting, or shared hosting. Each hosting type can have its unique I/O characteristics, and understanding these can help you further optimize performance.

Moreover, while tools like Seeker offer valuable insights, it’s essential to consider the results in conjunction with other performance metrics and real-world usage scenarios. For instance, a storage device with excellent random seek performance might still struggle with large sequential data transfers, or vice versa. Therefore, it’s beneficial to use a combination of tools and tests to get a comprehensive view of your storage device’s capabilities.

Additionally, always ensure that you backup critical data before performing any tests or making changes to your storage configurations. While Seeker is non-destructive, unforeseen issues can arise, especially when dealing with hardware. Regular backups ensure that your data remains safe regardless of any unexpected outcomes.

Lastly, continuous monitoring and periodic testing are key. As your system evolves, with software updates, data accumulation, and potential hardware wear, performance can change. Regularly using Seeker and similar tools can help you stay ahead of potential issues, ensuring that your system remains optimized and performs at its best.

In conclusion, Seeker is a powerful tool in the arsenal of webmasters and system administrators looking to optimize storage performance on Linux machines. By understanding its capabilities and using it effectively, you can ensure that your storage devices are always operating at peak efficiency, leading to smoother system operations and better overall performance.


Leave a Reply

Your email address will not be published. Required fields are marked *