Prerequisites
-
Install Warp:
- Create an Object Storage bucket if you don’t have one.
-
Create an access key.
You need its AWS-like ID and secret key to run benchmark tests. When you create the access key by using the CLI, the AWS-like ID and secret key are specified in the
.status.aws_access_key_idand.status.secretparameters of the output.
How to run benchmark tests
The example below showcases how to check the maximum single-node performance for read and write operations. Warp provides multiple tests for S3 methods. If you want to test a different use case, see the Warp repository for documentation or contact technical support. To run benchmark tests:-
Prepare environment variables for the tests:
In the
S3_ENDPOINTvariable, specify the same region where your bucket is located. -
Test the read performance:
Adjust the following parameters to your workload profile:
-
--objects: Number of objects to upload. The default value is2500but for better test results, specify at least5000. -
--obj.size: Size of each generated object. Specify the value asnKiB,nMiBornGiB, for example,100KiB. The default value is10MiB. -
--duration(optional): Duration of the test. Specify the value asNm, for example,7m. The default value is 5 minutes. Run the test for at least 5–10 minutes to see how stable the performance is. -
--storage-class(optional): Storage class to use. SetSTANDARDorENHANCED_THROUGHPUT. If not specified, the default storage class of the bucket is applied. -
--concurrent: Runs multiple concurrent operations per Warp client and sets the number of these operations. The default value is20. Adjust the value, considering the following recommendations:- The value range should be within 32–200.
- For small objects, run the test with a higher concurrency. For large objects, run it with a lower concurrency.
-
-
Test the write performance:
Adjust the
--obj.sizeand--concurrentparameters in the same way as in the read performance test.