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

add clearer warning about performance of FUSE 

[Imported from Trac: page FAQ, version 107]
zooko 2014-08-05 20:41:24 +00:00
parent 3f9a9a40f7
commit ff9c03827b
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
FAQ.md

@ -165,9 +165,11 @@ Literal caps are supported for immutable files and immutable directories (see [t
**<a name="Q23_FUSE">Q23:</a> Can I access files stored in Tahoe-LAFS via FUSE?**
A:
Yes. Tahoe-LAFS comes with an [SFTP server]source:docs/frontends/FTP-and-SFTP.rst. If you point [sshfs](http://fuse.sourceforge.net/sshfs.html) at the SFTP server then you have access to Tahoe-LAFS through FUSE. Alternately, [pyfilesystem](pyFilesystem) interfaces directly with Tahoe-LAFS through the latter's [web-API]source:docs/frontends/webapi.rst and provides both FUSE and Microsoft Windows filesystem access. See #1353 for discussion of possible improvements to FUSE integration.
Yes, but it is not recommended because while it will work for certain usages, its performance will crawl to a halt for other usages. You can try it and see if your particular uses happen to fit into its performance contours.
There could be performance problems with the FUSE interface if the apps that are using the filesystem use it in a way that doesn't fit Tahoe-LAFS's semantics, and the FUSE layer is required to make many copies of entire files in order to emulate the desired semantics. See [Zooko's post to freedombox-discuss](http://lists.alioth.debian.org/pipermail/freedombox-discuss/2011-November/003162.html) and [Zooko's post to Google+](https://plus.google.com/108313527900507320366/posts/ZrgdgLhV3NG).
Tahoe-LAFS comes with an [SFTP server]source:docs/frontends/FTP-and-SFTP.rst. If you point [sshfs](http://fuse.sourceforge.net/sshfs.html) at the SFTP server then you have access to Tahoe-LAFS through FUSE. Alternately, [pyfilesystem](pyFilesystem) interfaces directly with Tahoe-LAFS through the latter's [web-API]source:docs/frontends/webapi.rst and provides both FUSE and Microsoft Windows filesystem access. See #1353 for discussion of possible improvements to FUSE integration.
There will be fatal performance problems with the FUSE interface if your apps use it in a way that doesn't fit Tahoe-LAFS's semantics, and the FUSE layer is required to make many copies of entire files in order to emulate the desired semantics. See [Zooko's post to freedombox-discuss](http://lists.alioth.debian.org/pipermail/freedombox-discuss/2011-November/003162.html) and [Zooko's post to Google+](https://plus.google.com/108313527900507320366/posts/ZrgdgLhV3NG).
*'<a name="Q24_smallgrid">Q24:</a> How I should setup k,h,N on my small private grid?*