Skip to main content
Stroppy
Benchmarks
Published results
Leaderboard
Every public run, filter by engine and hardware
Protocol conformity
Which databases really speak the protocol they claim
In Stroppy Cloud
The leaderboard full screen, every filter
Studies
Client overhead
How fast the load generator itself is
Case studies
Benchmarks and what we learned from them
PostgreSQL 18
32 vCPU · 128 GB
13,283
tps
MySQL 8.4
32 vCPU · 128 GB
9,249
tps
MariaDB 11.8
32 vCPU · 128 GB
7,119
tps
Who is ahead right now
Published runs on the same workload, each with its full report.
Open the leaderboard →
How it works
Run a benchmark
Stroppy Cloud
Pick a database and a workload, get a report
Stroppy CLI
Open source, one binary, any database it can reach
Auto tuning
Every engine set up for its machine
Keep measuring
Suites & schedules
Compare variants at once, catch regressions nightly
Compare & share
Runs side by side, reports by a public link
API & CI
Launch from a pipeline, hear back by webhook
How Stroppy Cloud works
What you describe, what comes up for you, and what stays after the run.
See how it works →
Docs
Learn
Getting started
Install Stroppy and run a first test
Documentation
Drivers, configs, presets, reports
Workloads
TPC-B, TPC-C, TPC-H and TPC-DS in detail
Changelog
What changed in every release
Community
Blog
Engineering notes and benchmark write-ups
Discord
Ask the team and other users
GitHub
Source, issues and releases
Why Stroppy moved off k6
One Go binary instead of k6 and TypeScript, and what it did to the numbers.
Read the post →
Sign in
Tags
A
architecture
1
B
benchmark
2
C
ci
1
cli
3
D
drivers
2
G
github-actions
1
go
3
go-tpc
1
K
k6
1
M
metrics
2
monitoring
1
mysql
1
O
orioledb
2
P
performance
2
postgresql
2
R
release
3
S
stroppy
1
T
tpc-c
3
transactions
1
V
v6
1
W
workloads
2