diff --git a/FAQ.md b/FAQ.md index 9200b92..0e0cc60 100644 --- a/FAQ.md +++ b/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. For more details read [Garbage Collection in Tahoe](https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/garbage-collection.rst). + +**Q29: 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). \ No newline at end of file