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

add mostly-download load test data 

[Imported from Trac: page Performance, version 25]
warner 2007-12-19 04:13:07 +00:00
parent 8aca7f7f77
commit 8847b05e78
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
Performance.md

@ -177,6 +177,23 @@ Load is about the same as before, but of course the bandwidths are larger.
For this file size, the per-file overhead seems to be more of a limiting
factor than per-byte overhead.
### test three: 80% upload, 20% download, 1MB mean file size
Same environment as test 2, but 80% of the operations are uploads.
```
clients: 150kBps down, 680kBps up, .14 fps down, .67 fps up
tahoecs1: 62% CPU, 11Mbps out, 2.9Mbps in, load avg .85
tahoecs2: 57% CPU, 10Mbps out, 4Mbps in, load avg .76
tahoebs4: 16% CPU, 700kBps out, 5.4Mbps in, load avg 0.4ish
tahoebs5: 21%, 870kBps out, 5.1Mbps in, load avg about 0.35
```
Overall throughput is about half of the download case. Either uploading files
or modifying the dirnodes looks to be more expensive than downloading. The
CPU usage on the web servers was lower, suggesting that the expense might be
in round trips rather than actual computation.
### initial conclusions
So far, Tahoe is scaling as designed: the client nodes are the ones doing