Benchmark Summary | Tigris Object Storage Documentation
On this page
This page summarizes all benchmark results comparing Tigris with AWS S3 and Cloudflare R2 for small object workloads (1 KB objects).
Key Results
| Metric | Tigris vs AWS S3 | Tigris vs Cloudflare R2 |
|---|---|---|
| Read throughput | 4x faster | 20x faster |
| Write throughput | 4x faster | 20x faster |
| Read p90 latency | 5x lower | 86x lower |
| Write p90 latency | 2.5x lower | 41x lower |
| Bulk load time | 31% faster | 10x faster |
Load Phase Summary
Loading 10 million 1 KB objects.
| Service | P50 Latency (ms) | P90 Latency (ms) | Runtime (sec) | Throughput (ops/sec) |
|---|---|---|---|---|
| Tigris | 16.799ms | 35.871ms | 6710.7sec | 1490.2ops/sec |
| S3 | 25.743ms (1.53x Tigris) |
37.791ms (1.05x Tigris) |
8826.4sec (1.32x Tigris) |
1133ops/sec (0.76x Tigris) |
| R2 | 197.119ms (11.73x Tigris) |
340.223ms (9.48x Tigris) |
72063sec (10.74x Tigris) |
138.8ops/sec (0.09x Tigris) |
Total load time for loading 10M 1 KB objects
Read Performance Summary
Mixed workload (80% read, 20% write) - 1 million operations.
| Service | P50 Latency (ms) | P90 Latency (ms) | Runtime (sec) | Throughput (ops/sec) |
|---|---|---|---|---|
| Tigris | 5.399ms | 7.867ms | 241.7sec | 3309.8ops/sec |
| S3 | 22.415ms (4.15x Tigris) |
42.047ms (5.34x Tigris) |
896.8sec (3.71x Tigris) |
891.5ops/sec (0.27x Tigris) |
| R2 | 605.695ms (112.19x Tigris) |
680.959ms (86.56x Tigris) |
4705.3sec (19.47x Tigris) |
42.6ops/sec (0.01x Tigris) |
Write Performance Summary
Mixed workload (80% read, 20% write) - 1 million operations.
| Service | P50 Latency (ms) | P90 Latency (ms) | Runtime (sec) | Throughput (ops/sec) |
|---|---|---|---|---|
| Tigris | 12.855ms | 16.543ms | 241.6sec | 828.1ops/sec |
| S3 | 26.975ms (2.1x Tigris) |
41.215ms (2.49x Tigris) |
896.8sec (3.71x Tigris) |
223.6ops/sec (0.27x Tigris) |
| R2 | 605.695ms (47.12x Tigris) |
680.959ms (41.16x Tigris) |
4705.3sec (19.48x Tigris) |
42.6ops/sec (0.05x Tigris) |
Conclusion
Tigris outperforms S3 and R2 for small object workloads. The performance advantage stems from Tigris's optimized architecture for small objects. While S3 and R2 struggle with high latency on small payloads (R2's p90 PUT latency reaches 340ms), Tigris maintains consistent low latency through intelligent object inlining, key coalescing, and LSM-backed caching.
These results demonstrate that Tigris can serve as a unified storage solution for mixed workloads, eliminating the need to maintain separate systems for small and large objects.
These benchmarks focus on small object workloads. If your application handles millions of small files (metadata, thumbnails, config objects, AI model checkpoints), Tigris offers significant performance advantages. For workloads requiring vendor-specific integrations, test with your actual access patterns.