| Provider | Plan | Cost per month | Disk space (GB) | Memory (GB) | Num Cores |
|---|---|---|---|---|---|
| Google Compute Engine | n2-highcpu-2 | $41.87 | 0 | 2.0 | 2 |
Learn how to read Sysbench test results
The cpu test is one of the most simple benchmarks in SysBench. In this mode each request consists in calculation of prime numbers up to a value specified by the --cpu-max-primes option. All calculations are performed using 64-bit integers. Each thread executes the requests concurrently until either the total number of requests or the total execution time exceed the limits specified with the common command line options.
| Test Name | total_time | per_request_avg | per_request_p95 | events_rate |
|---|---|---|---|---|
| Multithreaded | 30.00 s | 5.73 ms | 10.84 ms | 697.70 ops/sec |
| Single Thread | 30.00 s | 2.16 ms | 2.18 ms | 463.66 ops/sec |
This test mode can be used to produce various kinds of file I/O workloads. At the prepare stage Sysbench
creates a specified number of files with a specified total size, then at the run stage, each thread
performs specified I/O operations on this set of files.
Sysbench fileio tests are run in synchronous mode, all operations are buffered. All tests are run
with a number of threads that matches the number of vCPUs found in the instance with a minimum of 4.
| Test Name | read_transfer_rate | write_transfer_rate | avg_latency | p95_latency |
|---|---|---|---|---|
| Random Read 4k | 11.83 MiB/s | 0 MiB/s | 1.32 ms | 3.30 ms |
| Random Read-Write 4k | 6.57 MiB/s | 4.38 MiB/s | 0.63 ms | 3.25 ms |
| Random Write 4k | 0 MiB/s | 10.44 MiB/s | 0.66 ms | 3.96 ms |
| Sequential Read | 40.96 MiB/s | 0 MiB/s | 0.38 ms | 5.18 ms |
| Sequential Write | 0 MiB/s | 39.83 MiB/s | 0.17 ms | 0.06 ms |
Memory allocation and transfer speed.
| Test Name | total_time | transfer_rate | operations_rate |
|---|---|---|---|
| Read | 21.36 s | 9.36 GiB/sec | 9816987 ops/sec |
| Write | 15.38 s | 6.50 GiB/sec | 6817451 ops/sec |