I'm playing with bb-clientd and observing that performance doesn't seem great in some cases. From past experience with similar pprof profiles, I wanted to try passing some additional mount options to FUSE to check if they make any difference, but this is currently not possible.
Right now, the configuration offers a way to set AllowOther and DirectMount but nothing else. What do you think about extending this to support other options exposed by FUSE according to fuse.MountOptions? The proto would expose the individual options, or it would simply allow passing a collection of strings via the Options field, as these are passed verbatim to the FUSE mount.
I'm playing with bb-clientd and observing that performance doesn't seem great in some cases. From past experience with similar pprof profiles, I wanted to try passing some additional mount options to FUSE to check if they make any difference, but this is currently not possible.
Right now, the configuration offers a way to set
AllowOtherandDirectMountbut nothing else. What do you think about extending this to support other options exposed by FUSE according tofuse.MountOptions? The proto would expose the individual options, or it would simply allow passing a collection of strings via theOptionsfield, as these are passed verbatim to the FUSE mount.