Skip to content

Commit fe79e6d

Browse files
committed
docs: simplify minio results
Just point to the real HTML results. Signed-off-by: Luis Chamberlain <[email protected]>
1 parent 903d6c0 commit fe79e6d

File tree

2 files changed

+3
-121
lines changed

2 files changed

+3
-121
lines changed

docs/minio-warp/README.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -196,13 +196,7 @@ After running benchmarks, you'll find:
196196

197197
### Demo Results
198198

199-
Example benchmark results are available in [demo-results/](demo-results/README.md) showing:
200-
- Performance graphs from 6 different benchmark scenarios
201-
- Throughput measurements ranging from 380-520 MB/s
202-
- Latency statistics and IOPS performance metrics
203-
- Tests ranging from 2 minutes to over 1 hour duration
204-
205-
View the [demo results analysis](demo-results/README.md) for detailed performance metrics and graphs.
199+
Example benchmark results are available in [demo-results/](demo-results/) containing throughput graphs from actual MinIO Warp test runs.
206200

207201
## Performance Analysis Tools
208202

Lines changed: 2 additions & 114 deletions
Original file line numberDiff line numberDiff line change
@@ -1,117 +1,5 @@
11
# MinIO Warp Demo Results
22

3-
This directory contains example benchmark results from MinIO Warp S3 performance testing demonstrating the capabilities of the kdevops MinIO workflow.
3+
View the benchmark report: [warp_benchmark_report.html](https://htmlpreview.github.io/?https://github.com/linux-kdevops/kdevops/blob/main/docs/minio-warp/demo-results/warp_benchmark_report.html)
44

5-
## Test Configuration
6-
7-
- **System**: Demo system with NVMe storage
8-
- **Filesystem**: XFS with 4K block size
9-
- **MinIO**: Single-node deployment via Docker
10-
- **Warp**: Full benchmark suite with mixed workloads
11-
12-
## Performance Results Summary
13-
14-
### Throughput Graphs
15-
16-
The following graphs show S3 operation throughput over time for different benchmark runs:
17-
18-
#### Run 1 - Mixed Workload (2:39 duration)
19-
![Throughput Graph 1](warp_benchmark_demo-0001_1756602074_throughput.png)
20-
- Peak throughput: ~450 MB/s
21-
- Average throughput: ~380 MB/s
22-
- Operations: Mixed GET/PUT/DELETE
23-
24-
#### Run 2 - GET Operations Focus (6:59 duration)
25-
![Throughput Graph 2](warp_benchmark_demo-0001_1756602501_throughput.png)
26-
- Peak GET throughput: ~520 MB/s
27-
- Sustained read performance
28-
- Consistent operation latency
29-
30-
#### Run 3 - PUT Operations Focus (12:14 duration)
31-
![Throughput Graph 3](warp_benchmark_demo-0001_1756603275_throughput.png)
32-
- Peak PUT throughput: ~480 MB/s
33-
- Write-heavy workload performance
34-
- Stable upload speeds
35-
36-
#### Run 4 - Large Object Testing (32:27 duration)
37-
![Throughput Graph 4](warp_benchmark_demo-0001_1756604480_throughput.png)
38-
- Large file operations (10MB objects)
39-
- Multipart upload performance
40-
- Bandwidth utilization patterns
41-
42-
#### Run 5 - High Concurrency Test (58:43 duration)
43-
![Throughput Graph 5](warp_benchmark_demo-0001_1756606036_throughput.png)
44-
- 32 concurrent connections
45-
- Stress test performance
46-
- Queue depth impact analysis
47-
48-
#### Run 6 - Extended Duration Test (1:06:32)
49-
![Throughput Graph 6](warp_benchmark_demo-0001_1756606513_throughput.png)
50-
- Long-running stability test
51-
- Performance consistency over time
52-
- No degradation observed
53-
54-
## Key Performance Metrics
55-
56-
### Mixed Workload Performance
57-
- **GET Operations**: 450-520 MB/s throughput
58-
- **PUT Operations**: 380-480 MB/s throughput
59-
- **DELETE Operations**: 15,000+ ops/sec
60-
- **LIST Operations**: 2,000+ ops/sec
61-
62-
### Latency Statistics
63-
- **GET P50**: 12ms
64-
- **GET P99**: 45ms
65-
- **PUT P50**: 18ms
66-
- **PUT P99**: 62ms
67-
68-
### IOPS Performance
69-
- **Read IOPS**: 12,000-15,000
70-
- **Write IOPS**: 8,000-10,000
71-
- **Mixed IOPS**: 10,000-12,000
72-
73-
## Test Methodology
74-
75-
Each benchmark run used the following Warp parameters:
76-
- Object size: 10 MiB (default)
77-
- Duration: 120 seconds minimum
78-
- Concurrency: 16 threads (except high-concurrency test)
79-
- Bucket count: 1
80-
- Object count: 1000
81-
82-
## Observations
83-
84-
1. **Consistent Performance**: MinIO maintains stable throughput across extended test runs
85-
2. **Linear Scaling**: Performance scales well with increased concurrency up to 32 threads
86-
3. **Low Latency**: P50 latencies remain under 20ms for most operations
87-
4. **Storage Efficiency**: XFS with 4K blocks provides good balance of performance and space utilization
88-
89-
## Running Your Own Tests
90-
91-
To reproduce these results or run your own benchmarks:
92-
93-
```bash
94-
# Use the same configuration as demo
95-
make defconfig-minio-warp-xfs
96-
make bringup
97-
make minio
98-
make minio-warp
99-
100-
# View your results
101-
make minio-results
102-
ls -la workflows/minio/results/
103-
```
104-
105-
## Full HTML Report
106-
107-
For detailed analysis, view the [complete benchmark report](warp_benchmark_report.html) locally after downloading.
108-
109-
## Graph Analysis
110-
111-
The throughput graphs demonstrate:
112-
- **Warm-up period**: Initial 10-15 seconds show ramp-up
113-
- **Steady state**: Consistent performance after warm-up
114-
- **No degradation**: Performance remains stable even in hour-long tests
115-
- **Burst capability**: System can handle traffic spikes effectively
116-
117-
These results validate MinIO's performance characteristics for S3-compatible workloads and demonstrate the effectiveness of the kdevops testing framework for storage benchmarking.
5+
This uses GitHub HTML Preview to render the HTML file directly in your browser.

0 commit comments

Comments
 (0)