diff --git a/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-start.adoc b/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-start.adoc index 2fad68714..e54dc9f56 100644 --- a/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-start.adoc +++ b/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-start.adoc @@ -3,6 +3,8 @@ Starts one or more benchmark tests on one or more nodes of the cluster. +NOTE: Redpanda self-test runs benchmarks that consume significant system resources. Do not start self-test if large workloads are already running on the system. + Available tests to run: * *Disk tests* @@ -14,7 +16,7 @@ Available tests to run: ** Throughput test: 8192-bit messages *** Unique pairs of Redpanda nodes each act as a client and a server. *** The test pushes as much data over the wire, within the test parameters. -* *Cloud tests* +* *Cloud storage tests* ** Latency test: 1024-bit object. ** Depending on cluster read/write permissions (xref:reference:properties/object-storage-properties.adoc#cloud_storage_enable_remote_read[`cloud_storage_enable_remote_read`], xref:reference:properties/object-storage-properties.adoc#cloud_storage_enable_remote_write[`cloud_storage_enable_remote_write`]), a series of cloud storage operations are performed: *** Upload an object to an object storage. @@ -22,9 +24,9 @@ Available tests to run: *** Download an object from the object storage. *** Delete the original object from the object storage, if it was uploaded. -This command immediately returns on success, and the tests run asynchronously. The -user polls for results with the xref:./rpk-cluster-self-test-status.adoc[rpk cluster self-test status] -command. +This command prompts users for confirmation (unless the flag `--no-confirm` is specified), then returns a test identifier ID, and runs the tests. + +To view the test status, poll xref:./rpk-cluster-self-test-status.adoc[rpk cluster self-test status]. Once the tests end, the cached results will be available with `rpk cluster self-test status`. == Usage @@ -39,21 +41,27 @@ rpk cluster self-test start [flags] |=== |*Value* |*Type* |*Description* -|--disk-duration-ms |duration |uint The in milliseconds of individual -disk test runs (default 30000). +|--cloud-backoff-ms |uint | The backoff in milliseconds for a cloud storage request (default `100`). + +|--cloud-timeout-ms |uint | The timeout in milliseconds for a cloud storage request (default `5000`). + +|--disk-duration-ms |uint | The duration in milliseconds of individual +disk test runs (default `30000`). |-h, --help |- |Help for start. -|--network-duration-ms |duration |uint The in milliseconds of individual -network test runs (default 30000). +|--network-duration-ms |uint | The duration in milliseconds of individual +network test runs (default `30000`). |--no-confirm |- |Acknowledge warning prompt skipping read from stdin. +|--only-cloud-test |- |Runs only cloud storage benchmarks. + |--only-disk-test |- |Runs only the disk benchmarks. |--only-network-test |- |Runs only network benchmarks. -|--participant-node-ids |- |ints IDs of nodes that the tests will run +|--participant-node-ids |uints |Comma-separated list of broker IDs that the tests will run on. If not set, tests will run for all node IDs. |--config |string |Redpanda or `rpk` config file; default search paths are `/var/lib/redpanda/.config/rpk/rpk.yaml`, `$PWD/redpanda.yaml`, and `/etc/redpanda/redpanda.yaml`. diff --git a/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-status.adoc b/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-status.adoc index f213ca38a..9ba5f2015 100644 --- a/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-status.adoc +++ b/modules/reference/pages/rpk/rpk-cluster/rpk-cluster-self-test-status.adoc @@ -1,15 +1,37 @@ = rpk cluster self-test status :description: Reference for the 'rpk cluster self-test status' command. Queries the status of the currently running or last completed self-test run. -Queries the status of the currently running or last completed self-test run. Returns the status of the currently running or last completed self-test run. +Returns the status of the current running tests or the cached results of the last completed run. Use this command after invoking xref:./rpk-cluster-self-test-start.adoc[rpk cluster self-test start] to determine the status of the jobs launched. Possible results are: * One or more jobs still running -** Returns the IDs of Redpanda nodes still running self-tests. +** Returns the IDs of Redpanda brokers (nodes) still running self-tests. Example: + +[,bash,role=no-copy] +---- +Node 1 is still running net self test +---- + * No jobs running -** Returns cached results for all nodes of the last completed test. +** Returns the cached results for all brokers of the last completed test. + +Test results are grouped by broker ID. Each test returns the following: + +* *Name*: Description of the test. +* *Info*: Details about the test run attached by Redpanda. +* *Type*: Either `disk`, `network`, or `cloud` test. +* *Test Id*: Unique identifier given to jobs of a run. All IDs in a test should match. If they don't match, then newer and/or older test results have been included erroneously. +* *Timeouts*: Number of timeouts incurred during the test. +* *Start time*: Time that the test started, in UTC. +* *End time*: Time that the test ended, in UTC. +* *Avg Duration*: Duration of the test. +* *IOPS*: Number of operations per second. For disk, it's `seastar::dma_read` and `seastar::dma_write`. For network, it's `rpc.send()`. +* *Throughput*: For disk, throughput rate is in bytes per second. For network, throughput rate is in bits per second. Note that GiB vs. Gib is the correct notation displayed by the UI. +* *Latency*: 50th, 90th, etc. percentiles of operation latency, reported in microseconds (μs). Represented as P50, P90, P99, P999, and MAX respectively. + +If xref:manage:tiered-storage.adoc[Tiered Storage] is not enabled, the cloud storage tests won't run and a warning will be displayed showing "Cloud storage is not enabled.". All results will be shown as 0. == Usage @@ -24,7 +46,7 @@ rpk cluster self-test status [flags] |=== |*Value* |*Type* |*Description* -|--format |string |Output format. Possible values: `json`, `yaml`, `text`, `wide`, `help`. Default: `text`. +|--format |string |Output format. Possible values: `json`, `text`. Default: `text`. |-h, --help |- |Help for status. @@ -38,226 +60,383 @@ rpk cluster self-test status [flags] |=== -== Example output +== Example -Test results are grouped by node ID. Each test returns the following: +Example input: + +[,bash] +---- +rpk cluster self-test status +---- -* *NAME*: Description of the test. -* *INFO*: Detail about the test run attached by Redpanda itself. -* *TYPE*: Either `disk` or `network` test. -* *TEST ID*: Unique identifier given to jobs of a run. All IDs in a test should match. If they don't match, then newer and/or older test results have been included erroneously. -* *TIMEOUTS*: Number of timeouts incurred during the test. -* *DURATION*: Duration of the test. -* *IOPS*: Number of operations per second. For disk, it's `seastar::dma_read` and `seastar::dma_write`. For network, it's `rpc.send()` -* *THROUGHPUT*: For disk, it's throughput rate in bytes per second. For network, it's throughput rate in bits per second in. (Note: GiB vs. Gib is the correct notation displayed by the UI.) -* *LATENCY*: 50th, 90th, etc. percentiles of operation latency, reported in microseconds. +Example output, for three-broker cluster: -[,console] +[,bash] ---- -$ rpk cluster self-test status NODE ID: 1 | STATUS: IDLE ========================= -NAME 512K sequential r/w throughput disk test -INFO write run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5001ms -IOPS 1590 req/sec -THROUGHPUT 795.2MiB/sec -LATENCY P50 P90 P99 P999 MAX - 831us 5887us 11263us 24575us 507903us - -NAME 512K sequential r/w throughput disk test -INFO read run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5001ms -IOPS 4504 req/sec -THROUGHPUT 2.2GiB/sec -LATENCY P50 P90 P99 P999 MAX - 703us 1599us 4351us 6399us 10239us - -NAME 4k sequential r/w latency/iops disk test -INFO write run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5031ms -IOPS 289 req/sec -THROUGHPUT 144.7MiB/sec -LATENCY P50 P90 P99 P999 MAX - 543us 34815us 69631us 77823us 77823us - -NAME 4k sequential r/w latency/iops disk test -INFO read run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 8275 req/sec -THROUGHPUT 4.041GiB/sec -LATENCY P50 P90 P99 P999 MAX - 191us 447us 831us 2175us 278527us - -NAME 8K Network Throughput Test -INFO Test performed against node: 0 -TYPE network -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 61254 req/sec -THROUGHPUT 3.74Gib/sec -LATENCY P50 P90 P99 P999 MAX - 159us 207us 303us 415us 1087us - -NAME 8K Network Throughput Test -INFO Test performed against node: 2 -TYPE network -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 54814 req/sec -THROUGHPUT 3.35Gib/sec -LATENCY P50 P90 P99 P999 MAX - 167us 255us 367us 511us 25599us +NAME 512KB sequential r/w throughput disk test +INFO write run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:58:13 UTC 2024 +END TIME Thu Jul 11 18:58:43 UTC 2024 +AVG DURATION 30007ms +IOPS 140 req/sec +THROUGHPUT 70.17MiB/sec +LATENCY P50 P90 P99 P999 MAX + 24575us 47103us 188415us 425983us 507903us + +NAME 512KB sequential r/w throughput disk test +INFO read run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:58:43 UTC 2024 +END TIME Thu Jul 11 18:59:13 UTC 2024 +AVG DURATION 30008ms +IOPS 276 req/sec +THROUGHPUT 138.5MiB/sec +LATENCY P50 P90 P99 P999 MAX + 13823us 19455us 24575us 57343us 77823us + +NAME 4KB sequential r/w latency/iops disk test +INFO write run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:59:13 UTC 2024 +END TIME Thu Jul 11 18:59:43 UTC 2024 +AVG DURATION 30000ms +IOPS 6769 req/sec +THROUGHPUT 26.44MiB/sec +LATENCY P50 P90 P99 P999 MAX + 191us 255us 2303us 13311us 81919us + +NAME 4KB sequential r/w latency/iops disk test +INFO read run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:59:43 UTC 2024 +END TIME Thu Jul 11 19:00:13 UTC 2024 +AVG DURATION 30001ms +IOPS 13235 req/sec +THROUGHPUT 51.7MiB/sec +LATENCY P50 P90 P99 P999 MAX + 127us 239us 735us 1919us 63487us + +NAME 8Kb Network Throughput Test +INFO Test performed against node: 2 +TYPE network +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 19:00:13 UTC 2024 +END TIME Thu Jul 11 19:00:43 UTC 2024 +AVG DURATION 30000ms +IOPS 55370 req/sec +THROUGHPUT 3.38Gib/sec +LATENCY P50 P90 P99 P999 MAX + 167us 231us 351us 495us 7679us + +NAME Cloud Storage Test +INFO Put +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 8ms + +NAME Cloud Storage Test +INFO List +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Get +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Head +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 0ms + +NAME Cloud Storage Test +INFO Delete +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Plural Delete +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 47ms -NODE ID: 0 | STATUS: IDLE +NODE ID: 2 | STATUS: IDLE ========================= -NAME 512K sequential r/w throughput disk test -INFO write run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5002ms -IOPS 1593 req/sec -THROUGHPUT 796.8MiB/sec -LATENCY P50 P90 P99 P999 MAX - 735us 5887us 11263us 69631us 507903us - -NAME 512K sequential r/w throughput disk test -INFO read run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 4372 req/sec -THROUGHPUT 2.135GiB/sec -LATENCY P50 P90 P99 P999 MAX - 735us 1599us 4351us 7423us 9215us - -NAME 4k sequential r/w latency/iops disk test -INFO write run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5026ms -IOPS 286 req/sec -THROUGHPUT 143.1MiB/sec -LATENCY P50 P90 P99 P999 MAX - 543us 34815us 69631us 77823us 77823us - -NAME 4k sequential r/w latency/iops disk test -INFO read run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 8269 req/sec -THROUGHPUT 4.038GiB/sec -LATENCY P50 P90 P99 P999 MAX - 191us 447us 831us 2175us 278527us - -NAME 8K Network Throughput Test -INFO Test performed against node: 1 -TYPE network -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 61612 req/sec -THROUGHPUT 3.76Gib/sec -LATENCY P50 P90 P99 P999 MAX - 159us 207us 303us 431us 1151us - -NAME 8K Network Throughput Test -INFO Test performed against node: 2 -TYPE network -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 60306 req/sec -THROUGHPUT 3.68Gib/sec -LATENCY P50 P90 P99 P999 MAX - 159us 215us 351us 495us 11263us +NAME 512KB sequential r/w throughput disk test +INFO write run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:58:13 UTC 2024 +END TIME Thu Jul 11 18:58:43 UTC 2024 +AVG DURATION 30006ms +IOPS 141 req/sec +THROUGHPUT 70.52MiB/sec +LATENCY P50 P90 P99 P999 MAX + 24575us 47103us 188415us 409599us 507903us + +NAME 512KB sequential r/w throughput disk test +INFO read run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:58:43 UTC 2024 +END TIME Thu Jul 11 18:59:13 UTC 2024 +AVG DURATION 30011ms +IOPS 279 req/sec +THROUGHPUT 139.5MiB/sec +LATENCY P50 P90 P99 P999 MAX + 13823us 19455us 24575us 57343us 81919us + +NAME 4KB sequential r/w latency/iops disk test +INFO write run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:59:13 UTC 2024 +END TIME Thu Jul 11 18:59:43 UTC 2024 +AVG DURATION 29999ms +IOPS 7045 req/sec +THROUGHPUT 27.52MiB/sec +LATENCY P50 P90 P99 P999 MAX + 191us 255us 2303us 13823us 81919us + +NAME 4KB sequential r/w latency/iops disk test +INFO read run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:59:43 UTC 2024 +END TIME Thu Jul 11 19:00:13 UTC 2024 +AVG DURATION 30000ms +IOPS 13064 req/sec +THROUGHPUT 51.03MiB/sec +LATENCY P50 P90 P99 P999 MAX + 127us 247us 767us 2175us 61439us + +NAME Cloud Storage Test +INFO Put +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 8ms + +NAME Cloud Storage Test +INFO List +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Get +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Head +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 0ms + +NAME Cloud Storage Test +INFO Delete +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Plural Delete +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 47ms -NODE ID: 2 | STATUS: IDLE +NODE ID: 0 | STATUS: IDLE ========================= -NAME 512K sequential r/w throughput disk test -INFO write run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5001ms -IOPS 1580 req/sec -THROUGHPUT 790MiB/sec -LATENCY P50 P90 P99 P999 MAX - 671us 5887us 12287us 47103us 507903us - -NAME 512K sequential r/w throughput disk test -INFO read run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 3932 req/sec -THROUGHPUT 1.92GiB/sec -LATENCY P50 P90 P99 P999 MAX - 831us 1791us 4351us 7167us 9215us - -NAME 4k sequential r/w latency/iops disk test -INFO write run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5027ms -IOPS 280 req/sec -THROUGHPUT 140.1MiB/sec -LATENCY P50 P90 P99 P999 MAX - 575us 34815us 73727us 86015us 86015us - -NAME 4k sequential r/w latency/iops disk test -INFO read run -TYPE disk -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 8699 req/sec -THROUGHPUT 4.248GiB/sec -LATENCY P50 P90 P99 P999 MAX - 183us 367us 831us 2175us 278527us - -NAME 8K Network Throughput Test -INFO Test performed against node: 0 -TYPE network -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 60027 req/sec -THROUGHPUT 3.66Gib/sec -LATENCY P50 P90 P99 P999 MAX - 159us 223us 351us 511us 11775us - -NAME 8K Network Throughput Test -INFO Test performed against node: 1 -TYPE network -TEST ID 5e4052f3-b828-4c0d-8fd0-b34ff0b6c35d -TIMEOUTS 0 -DURATION 5000ms -IOPS 63090 req/sec -THROUGHPUT 3.85Gib/sec -LATENCY P50 P90 P99 P999 MAX - 151us 207us 319us 463us 17407us +NAME 512KB sequential r/w throughput disk test +INFO write run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:58:13 UTC 2024 +END TIME Thu Jul 11 18:58:43 UTC 2024 +AVG DURATION 30009ms +IOPS 140 req/sec +THROUGHPUT 70.38MiB/sec +LATENCY P50 P90 P99 P999 MAX + 24575us 47103us 180223us 360447us 507903us + +NAME 512KB sequential r/w throughput disk test +INFO read run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:58:43 UTC 2024 +END TIME Thu Jul 11 18:59:13 UTC 2024 +AVG DURATION 30005ms +IOPS 278 req/sec +THROUGHPUT 139.2MiB/sec +LATENCY P50 P90 P99 P999 MAX + 13823us 19455us 24575us 57343us 77823us + +NAME 4KB sequential r/w latency/iops disk test +INFO write run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:59:13 UTC 2024 +END TIME Thu Jul 11 18:59:43 UTC 2024 +AVG DURATION 30000ms +IOPS 6767 req/sec +THROUGHPUT 26.43MiB/sec +LATENCY P50 P90 P99 P999 MAX + 191us 255us 2303us 13823us 102399us + +NAME 4KB sequential r/w latency/iops disk test +INFO read run +TYPE disk +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 18:59:43 UTC 2024 +END TIME Thu Jul 11 19:00:13 UTC 2024 +AVG DURATION 30003ms +IOPS 13206 req/sec +THROUGHPUT 51.59MiB/sec +LATENCY P50 P90 P99 P999 MAX + 123us 239us 735us 1855us 63487us + +NAME 8Kb Network Throughput Test +INFO Test performed against node: 1 +TYPE network +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 19:00:13 UTC 2024 +END TIME Thu Jul 11 19:00:43 UTC 2024 +AVG DURATION 30000ms +IOPS 34929 req/sec +THROUGHPUT 2.13Gib/sec +LATENCY P50 P90 P99 P999 MAX + 303us 367us 511us 671us 6399us + +NAME 8Kb Network Throughput Test +INFO Test performed against node: 2 +TYPE network +TEST ID 5632cefe-cf42-44ab-bba9-18fa1c71e3ee +TIMEOUTS 0 +START TIME Thu Jul 11 19:00:43 UTC 2024 +END TIME Thu Jul 11 19:01:13 UTC 2024 +AVG DURATION 30000ms +IOPS 86498 req/sec +THROUGHPUT 5.28Gib/sec +LATENCY P50 P90 P99 P999 MAX + 107us 151us 247us 351us 10239us + +NAME Cloud Storage Test +INFO Put +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 8ms + +NAME Cloud Storage Test +INFO List +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Get +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Head +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 0ms + +NAME Cloud Storage Test +INFO Delete +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 1ms + +NAME Cloud Storage Test +INFO Plural Delete +TYPE cloud +TEST ID a349685a-ee49-4141-8390-c302975db3a5 +TIMEOUTS 0 +START TIME Tue Jul 16 18:06:30 UTC 2024 +END TIME Tue Jul 16 18:06:30 UTC 2024 +AVG DURATION 47ms + + ---- NOTE: If self-test returns write results that are unexpectedly and significantly lower than read results, it may be because the Redpanda `rpk` client hardcodes the `DSync` option to `true`. When `DSync` is enabled, files are opened with the `O_DSYNC` flag set, and this represents the actual setting that Redpanda uses when it writes to disk.