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

add a few more performance notes 

[Imported from Trac: page Performance, version 35]
zooko 2011-07-15 19:20:50 +00:00
parent 164a4c4c56
commit 14f2c307fe
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
Performance.md

@ -26,4 +26,8 @@ At about the same time Nathan Eisenberg of Atlas Networks did a couple of manual
Also François Deppierraz has run a few benchmarks. (Can't find a link to his results.) Also François Deppierraz has run a few benchmarks. (Can't find a link to his results.)
Jeff Darcy benchmarked Tahoe-LAFS vs. his new CloudFS (based on Gluster) vs. encfs vs. ecryptfs vs. Gluster, using iozone: <https://fedorahosted.org/pipermail/cloudfs-devel/2011-June/000097.html> <https://fedorahosted.org/pipermail/cloudfs-devel/2011-June/000099.html>
Ticket #932 (benchmark Tahoe-LAFS compared to nosql dbs) is a ticket to run the standard "YCSB" benchmarks for nosql databases on Tahoe-LAFS.
What we *really* want, of course, is automated benchmarks that get executed at regularly scheduled intervals, or whenever a new patch is committed to revision control, or both. This would ideally run on some dedicated hardware or at least on some virtualized hardware which had a fairly consistent load of other tenants, so that the resulting measurements would not get too much noise from other people's behavior. You can see on Performance/Old that we used to have such an automated setup, including graphs of the resulting performance. What we *really* want, of course, is automated benchmarks that get executed at regularly scheduled intervals, or whenever a new patch is committed to revision control, or both. This would ideally run on some dedicated hardware or at least on some virtualized hardware which had a fairly consistent load of other tenants, so that the resulting measurements would not get too much noise from other people's behavior. You can see on Performance/Old that we used to have such an automated setup, including graphs of the resulting performance.