On 09/04/2014 07:31 AM, Nick Carboni wrote:
> I am using s3ql for an application that may require the user to read
> large amounts of data over an NFS (or CIFS) export of the s3ql file
> system. I came across the --nfs option for mount.s3ql which is
> described as enabling "some optimizations for exporting the file system
> over NFS." I'm assuming there is some downside to specifying this
> option as the default is false. Is there any documentation on what this
> option does and how it could hurt or help performance?
It increases the size of the local metadata database a bit, and it may
reduce overall performance of metadata operations a bit (because S3QL
has to keep an additional index up-to-date).
Conversely, it should significantly increase the performance of some NFS
requests, but I don't know how frequent this specific operation is
(lookup of . or .. by name).
As far as I know, no one has yet measured how big any of these effects
actually are.
Best,
-Niko
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to s3ql+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
