[Gluster-users] Confusing lstat() performance

[Niklas Hambüchen]

Note, I have now put out a patch for bup that makes it 50x faster on my
1M files on gluster, exploiting the fact that stat() is fast after
getdents() on it:

  https://groups.google.com/forum/#!topic/bup-list/6CM7Jr7b_Ek

I'd still be interested in answers to this question though:

> What caching could this be, and how could I convince gluster to serve
> these stat()s as fast as if a getdents() had been done just before them?