[Gluster-users] gluster 3.2.0 - totally broken?

[Tomasz Chmielewski]

On 20.05.2011 15:51, Stephan von Krawczynski wrote:

> most of them are just an outcome of not being able to find a working i.e. best
> solution for a problem. cache-timeout? thread-count? quick-read?
> stat-prefetch? Gimme a break. Being a fs I'd even say all the cache-size paras
> are bogus. When did you last tune the ext4 cache size or timeout? Don't come
> up with ext4 being kernel vs. userspace fs.  It was their decision to make it
> userspace, so don't blame me. As a fs with networking it has to take the
> comparison with nfs - as most interested users come from nfs.

Ever heard of fsc (FS-Cache), acreg*, acdir*, actimeo options for NFS?

Yes, they are related to cache, and oh, NFS is kernelspace. And yes, 
there are tunable timeout options for NFS as well.


As of timeout options with ext4, or any other local filesystem - if you 
ever used iSCSI, you would also discover that it's recommended to set 
reasonable timeout options there as well, depending on your network 
infrastructure and usage/maintenance patterns. "Incidentally", iSCSI is 
also kernelspace.


-- 
Tomasz Chmielewski
http://wpkg.org