Re: [Gluster-devel] Any mature(better) solution(way) to handle slow performance on 'ls -l, '.

Thanks for you kind reply, which is very helpful for me, I use 3.11, Thanks a lot. :-) - Fei On Thu, Jun 7, 2018 at 6:59 PM Poornima Gurusiddaiah wrote: > > If you are not using applications that rely on 100% metadata consistency, > like Databases, Kafka, AMQ etc. you can use the below mention

Re: [Gluster-devel] Any mature(better) solution(way) to handle slow performance on 'ls -l, '.

If you are not using applications that rely on 100% metadata consistency, like Databases, Kafka, AMQ etc. you can use the below mentioned volume options: # gluster volume set group metadata-cache # gluster volume set network.inode-lru-limit 20 # gluster volume set performance.readdir-ahea

[Gluster-devel] Any mature(better) solution(way) to handle slow performance on 'ls -l, '.

Hi experts on glusterFS, In our testbed, we found that the ' ls -l' performance is pretty slow. Indeed from the prospect of glusterFS design space, we need to avoid 'ls ' directory which will traverse all bricks sequentially in our current knowledge. We use generic setting for our testbed: ``` V