tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

fix relative links that are interpreted differently in this new version of trac 

[Imported from Trac: page Performance, version 29]
warner 2008-02-27 23:38:07 +00:00
parent ce6e18c02f
commit 15d382d956
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Performance.md

@ -58,11 +58,11 @@ Small files seem to be limited by a per-file overhead. Large files are limited
by the link speed. by the link speed.
The munin The munin
[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay.html delay graph] and [delay graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay.html) and
[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_rate.html rate graph] show these Ax+B numbers for a node in colo and a node behind a DSL line. [rate graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_rate.html) show these Ax+B numbers for a node in colo and a node behind a DSL line.
The The
[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay_rtt.html delay*RTT graph] shows this per-file delay as a multiple of the average round-trip [delay*RTT graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay_rtt.html) shows this per-file delay as a multiple of the average round-trip
time between the client node and the testnet. Much of the work done to upload time between the client node and the testnet. Much of the work done to upload
a file involves waiting for message to make a round-trip, so expressing the a file involves waiting for message to make a round-trip, so expressing the
per-file delay in units of RTT helps to compare the observed performance per-file delay in units of RTT helps to compare the observed performance
@ -80,11 +80,11 @@ this step.
There is also per-file overhead for upload and download, just like with CHK There is also per-file overhead for upload and download, just like with CHK
files, mostly involving the queries to find out which servers are holding files, mostly involving the queries to find out which servers are holding
which versions of the file. The which versions of the file. The
[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay_SSK.html mutable-file delay graph] [mutable-file delay graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_delay_SSK.html)
shows this "B" per-file latency value. shows this "B" per-file latency value.
The "A" transfer rate for SSK files is also tracked in this The "A" transfer rate for SSK files is also tracked in this
[/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_rate_SSK.html SSK rate graph]. [SSK rate graph](http://allmydata.org/tahoe-figleaf-graph/hanford.allmydata.com-tahoe_speedstats_rate_SSK.html).
### Roundtrips ### Roundtrips