Community Benchmark
Performance numbers, not capability checks. Each round measures real upload, download, list, stat and delete throughput across cloud providers, with statistical aggregates (p50, p95, stddev, min, max) over multiple runs.
The community benchmark is a separate workflow from the integration tests in this section: those check whether a feature works at all on a given backend, the benchmark measures how fast it works once it does. The two answer different questions and live side by side.
Submission flow
New reports go through the Community Benchmark Report issue template, one issue per report. The original call, axpdev-lab/aeroftp#177, is closed. The CLI ships aeroftp-cli benchmark since v3.7.3 (stabilized in v3.7.4) with strict sanitization: no hostnames, paths, credentials, bucket names, or account ids ever enter the JSON report.
Anyone can contribute their own region and connection type by running:
aeroftp-cli --profile "Your Profile" benchmark standard \
--consent-publish --report bench.jsonThen open a new issue with the template and paste the block printed between --- BEGIN BENCHMARK REPORT (paste into the GitHub Issue) --- and --- END BENCHMARK REPORT ---.
Rounds
| Round | CLI version | Profiles covered | Status |
|---|---|---|---|
| 2026-05-07 (maintainer baseline) | v3.7.3 / v3.7.4 | 35 sanitized reports (18 full matrix + 14 partial + 3 verify) | published |
Why the page exists
When AeroFTP claims that one protocol is faster than another on a given provider, that claim should be defensible. A single residential fiber line in a single timezone is not a credible base for a public protocol comparison page. Selection bias in the maintainer baseline is explicit and called out in each round's disclosure section. Real conclusions only come from aggregating across at least three regions and two connection types.