Opened at 2022-12-14T15:48:10Z
Last modified at 2023-08-17T17:14:07Z
#3955 new task
High-level benchmarking suite, as part of attempt to speed up Tahoe
Reported by: | itamarst | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Performance and Benchmarking |
Component: | unknown | Version: | n/a |
Keywords: | Cc: | ||
Launchpad Bug: |
Description (last modified by itamarst)
We should have a broader benchmarking attempt, involving:
- Defining metrics
- Defining goals
Two aspects:
- User experience
- Server-side load
UX is probably more important at this point, but eventually if that's finished server load will become an issue.
Metrics:
- Latency (single upload/download)
- Throughput (batch uploads/downloads)
Bottlenecks will be network latency, CPU, network bandwidth. If we've hit point where network bandwidth is the bottleneck, we're done optimizing.
Throughput depends on usage patterns of:
- tahoe cp
- tahoe backup
- sftp
- Magic Folders
- Third party backup tools that integrate with Tahoe (duplicaty? duplicati? borg?)
Knobs: number of backend storage servers, network latency.
Change History (4)
comment:1 Changed at 2022-12-14T15:48:28Z by itamarst
- Summary changed from High-level benchmarking suite to High-level benchmarking suite, as part of attempt to speed up Tahoe
comment:2 Changed at 2023-06-20T17:39:04Z by itamarst
- Description modified (diff)
comment:3 Changed at 2023-06-20T17:42:11Z by itamarst
comment:4 Changed at 2023-08-17T17:14:07Z by itamarst
- Milestone changed from undecided to Performance and Benchmarking
Note: See
TracTickets for help on using
tickets.
Might want to get https://github.com/tahoe-lafs/tahoe-lafs/pull/1208 merged and then rely on the code that was refactored out of the tests.