Benchmark skeleton

doc/benchmarks
Quentin Dufour 2 years ago
parent 8cd02639dc
commit 1be1715522
No known key found for this signature in database
GPG Key ID: E9602264D639FF68
  1. 8
      doc/book/benchmarks/_index.md
  2. 17
      doc/book/benchmarks/abstraction.md
  3. 18
      doc/book/benchmarks/failure_recovery.md
  4. 14
      doc/book/benchmarks/industry_tools.md
  5. 10
      doc/book/benchmarks/liveness.md
  6. 14
      doc/book/benchmarks/network_sensitiveness.md
  7. 16
      doc/book/benchmarks/pushing_limits.md
  8. 8
      doc/book/benchmarks/real_world.md
  9. 2
      doc/book/development/_index.md
  10. 2
      doc/book/working-documents/_index.md

@ -0,0 +1,8 @@
+++
title = "Benchmarks"
weight = 60
sort_by = "weight"
template = "documentation.html"
+++
Hello

@ -0,0 +1,17 @@
+++
title = "Abstraction cost"
weight = 30
+++
We take as our baseline the raw disk sequential write performance.
We then compare Garage's performances to it, the difference represents what we call our "abstraction cost".
fsync, chunking, compression, pipelining, synchronization
# raw perf VS garage
# garage tmpfs VS garage std
# garage various multipart sizes
# garage 0.7.2.1 VS upstream

@ -0,0 +1,18 @@
+++
title = "Failure & recovery"
weight = 50
+++
# Failure impact
Failures will lead to timeouts, which in turn could
lead to failed requests (this is a bug if failure enters in Garage tolerance)
and to increased latency as some retries might be performed.
How we proceed: we pause (`kill -STOP xxx`) one Garage process.
The idea is we don't want to close the TCP connection that would signal too easily
that a crash occured. Instead, we want to simulate a network error
or an overloaded process, ie. a 'non-collaborating' crash.
# Recovery impact

@ -0,0 +1,14 @@
+++
title = "Industry tools"
weight = 60
+++
# minio warp
# intel-cloud cosbench
# (non retenu)
- wasabi s3-benchmark
- https://github.com/dvassallo/s3-benchmark

@ -0,0 +1,10 @@
+++
title = "Liveness"
weight = 40
+++
freedom from starvation, backpressure, etc.
# Responsiveness under read/write load

@ -0,0 +1,14 @@
+++
title = "Network sensitiveness"
weight = 10
+++
impact of node count and their latency
# Latency amplification
# Cluster size impact
# Time-To-First-Byte (TTFB)
with various object size

@ -0,0 +1,16 @@
+++
title = "Pushing limits"
weight = 60
+++
# Many objects
# Huge objects
# Many nodes (horizontal scalability)
# Large nodes (vertical scalability)

@ -0,0 +1,8 @@
+++
title = "Real world"
weight = 80
+++
# Nextcloud
# Peertube

@ -1,6 +1,6 @@
+++
title = "Development"
weight = 6
weight = 70
sort_by = "weight"
template = "documentation.html"
+++

@ -1,6 +1,6 @@
+++
title = "Working Documents"
weight = 7
weight = 80
sort_by = "weight"
template = "documentation.html"
+++

Loading…
Cancel
Save