Benchmarking a new server hardware configuration
Every new server hardware configuration must be verified for minimum performance requirements set by Riverbed.
1. Repeat the installation process.
2. Configure the Edge on a new server.
3. Run the blockstore command.
4. Send the output to Riverbed Support.
5. Run the service storage restart clean command to start the Edge service.
Using the blockstore command may overwrite the contents of the blockstore, and the warning message below will display when you run the command. Before proceeding, you will be prompted to shut down the Edge service. If you want to ship the appliance to the customer, you must reinstall the Edge software on this appliance first.
edge> enable
edge (config) # blockstore run-all
WARNING! This test will erase the contents of the blockstore and read/write cache. Are you sure you
want to continue (y/n) ? [y/n] y
Edge service is running! Please bring it down and then run this test
Command to terminate 'edge' service : 'no service storage enable'
Command to resume 'edge' service : 'service storage restart clean'
Running the blockstore command
The blockstore command is available in the enable mode of the Riverbed CLI and measures the read/write I/O performance of the underlying disks. It runs five different I/O tests on the disk and reports the Input/Output Operations Per Second (IOPS).
Syntax
blockstore <type>
Parameters
<type> | Type of test: • run-all runs all tests. • r-8k-read-p1 runs random 8K aligned read test with parallelism = 1. • r-8k-read-p256 runs random 8K aligned test with parallelism = 256. • s-256k-read-p16 runs sequential read, 256K aligned, 16 parallel reads. • s-256k-wrt-p16 runs sequential 256K aligned write test with parallelism = 16 with cache pages. • s-8k-wrt-p1 runs sequential 8K aligned write test with parallelism = 1 with cache pages. |
Usage
We recommend that you use the run-all keyword to execute all the tests and display a consolidated report of each test. However, you may run individual tests if you prefer.
After running the blockstore command, enter the service storage restart clean command to start the Edge service.
Example
edge (config) # blockstore run-all
RESULT : Sequential 8K aligned write test. Parallelism = 1
----------------------------------------------------------
BsBench-Avg-response-time (ms) : 0.198177
BsBench-MBps-write : 39.4199
BsBench-IOps-write : 5045.95
BsBench-MBps-read : 0
BsBench-IOps-read : 0
----------------------------------------------------------
Edge process is not currently running
RESULT : Sequential 256K aligned write test. Parallelism = 16
----------------------------------------------------------
BsBench-Avg-response-time (ms) : 15.5941
BsBench-MBps-write : 256.479
BsBench-IOps-write : 1025.96
BsBench-MBps-read : 0
BsBench-IOps-read : 0
----------------------------------------------------------
Edge process is not currently running
RESULT : Random 8K aligned read test. Parallelism = 1
----------------------------------------------------------
BsBench-Avg-response-time (ms) : 0.544996
BsBench-MBps-write : 0
BsBench-IOps-write : 0
BsBench-MBps-read : 14.3199
BsBench-IOps-read : 1834.87
----------------------------------------------------------
Edge process is not currently running
RESULT : Random 8K aligned read test. Parallelism = 256
----------------------------------------------------------
BsBench-Avg-response-time (ms) : 20.5674
BsBench-MBps-write : 0
BsBench-IOps-write : 0
BsBench-MBps-read : 97.2239
BsBench-IOps-read : 12444.8
----------------------------------------------------------
Edge process is not currently running
RESULT : Sequential 256K aligned read test. Parallelism = 16
----------------------------------------------------------
BsBench-Avg-response-time (ms) : 16.2193
BsBench-MBps-write : 0
BsBench-IOps-write : 0
BsBench-MBps-read : 246.585
BsBench-IOps-read : 986.378