YGGverse/aquatic
1
0
Fork 0
mirror of https://github.com/YGGverse/aquatic.git synced 2026-03-31 17:55:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

README: add more aquatic_ws load test results

Browse source
This commit is contained in:
Joakim Frostegård 2021-08-19 11:47:33 +02:00 • committed by GitHub
parent f97994b4bb
commit c0f227b9f9
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 17 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

27
README.md
View file

@ -155,19 +155,26 @@ of the `aquatic_http` section above.
#### Benchmarks #### Benchmarks
Performance was compared to [wt-tracker]: https://github.com/Novage/wt-tracker
[wt-tracker](https://github.com/Novage/wt-tracker) and [bittorrent-tracker](https://github.com/webtorrent/bittorrent-tracker) using [bittorrent-tracker]: https://github.com/webtorrent/bittorrent-tracker
`aquatic_ws_load_test` with one worker, 16 connections and 2 offers per request.
| tracker | responses per second | Server responses per second, best result in bold:
|------------------------|----------------------|
| __aquatic__ | 126k |
| __wt-tracker__ | 54k |
| __bittorrent-tracker__ | 28k |
Both reference trackers reached 100% single-core utilization. | workers | aquatic | [wt-tracker] | [bittorrent-tracker] |
|---------|------------|--------------|----------------------|
| 1 | n/a | __117k__ | 45k |
| 2 | __225k__ | n/a | n/a |
| 4 | __627k__ | n/a | n/a |
| 6 | __831k__* | n/a | n/a |
| 8 | __1209k__* | n/a | n/a |
| 10 | __1455k__* | n/a | n/a |
| 12 | __1650k__* | n/a | n/a |
| 14 | __1804k__* | n/a | n/a |
| 16 | __1789k__* | n/a | n/a |
This benchmark is not very realistic, as it simulates a tiny number of clients, each sending a large number of requests. Nontheless, I think that it gives a useful indication of relative performance. \* Using a VPS with 32 vCPUs. The other measurements were made using a 16 vCPU VPS.
This benchmark is not very realistic, as it simulates a small number of clients, each sending a large number of requests. Nonetheless, I think that it gives a useful indication of relative performance.
## Load testing ## Load testing