search for: writeson

...rmance.nfs.strict-o-direct ? ? ? ? off ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? >> performance.strict-write-ordering ? ? ? off ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? >> performance.nfs.strict-write-ordering ? off ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? >> performance.write-behind-trickling-writeson ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? >> performance.aggregate-size ? ? ? ? ? ? ?128KB ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? >> performance.nfs.write-behind-trickling-writeson ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? >> performance.lazy-open ? ? ? ? ? ? ? ? ? yes ? ? ? ? ? ? ? ? ? ? ? ?...

...> performance.nfs.strict-o-direct ? ? ? ? off ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > performance.strict-write-ordering ? ? ? off ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > performance.nfs.strict-write-ordering ? off ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > performance.write-behind-trickling-writeson ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > performance.aggregate-size ? ? ? ? ? ? ?128KB ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > performance.nfs.write-behind-trickling-writeson ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? > performance.lazy-open ? ? ? ? ? ? ? ? ? yes ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?...

Hi David, On Dec 24, 2019 02:47, David Cunningham <dcunningham at voisonics.com> wrote: > > Hello, > > In testing we found that actually the GFS client having access to all 3 nodes made no difference to performance. Perhaps that's because the 3rd node that wasn't accessible from the client before was the arbiter node? It makes sense, as no data is being generated towards

Hi, On 03/19/2018 03:42 PM, TomK wrote: > On 3/19/2018 5:42 AM, Ondrej Valousek wrote: > Removing NFS or NFS Ganesha from the equation, not very impressed on my > own setup either.? For the writes it's doing, that's alot of CPU usage > in top. Seems bottle-necked via a single execution core somewhere trying > to facilitate read / writes to the other bricks. > >