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

[Imported from Trac: page FAQ, version 86]

luckyredhot 2013-03-14 13:12:56 +00:00
parent a9413cb8f0
commit c0601fe61f
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
FAQ.md

@ -196,3 +196,11 @@ A: Not yet, see ticket #867.
A: Tahoe-LAFS is designed to allow multiple users to access the same files. You wouldn't like it if one day a file of yours had been deleted by somebody else, right? Therefore, we have to solve The Garbage Collection Problem. The current solution is: do lease-renewal every month or so, and delete any files that nobody has lease-renewed in more than a month or so. A: Tahoe-LAFS is designed to allow multiple users to access the same files. You wouldn't like it if one day a file of yours had been deleted by somebody else, right? Therefore, we have to solve The Garbage Collection Problem. The current solution is: do lease-renewal every month or so, and delete any files that nobody has lease-renewed in more than a month or so.
For more details read [Garbage Collection in Tahoe](https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/garbage-collection.rst). For more details read [Garbage Collection in Tahoe](https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/garbage-collection.rst).
**<a name="Q29_bandwidth_performance">Q29:</a> What is actual operational read/write speed of Tahoe-LAFS grid?**
A: It depends on multiple factors starting from your hardware and ending with TPC/IP stack parameters. And much-much more!
Practically the following results have been reported: **16Mbps in throughput for writing and about 8.8Mbps in reading** (based on Grid of 24 storage nodes on 24 VM's running under [OpenStack](OpenStack) in 4 data centres; each VM had two 2 VCPU's, 4GB of RAM, and 50GB of disk space).
You can read the following section for more details: [Performance](https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Performance).