Re: Quick Question: glusterFS and kernel (stat) caching

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I second this request, any info on the problem?

Jim

On 8/6/07, Bernhard J. M. Grün <bernhard.gruen@xxxxxxxxxxxxxx> wrote:
>
> Hello developers!
>
> At the moment we try to optimize our web server setup again.
> We tried to parallelize the stat calls in our web server software
> (lighttpd). But it seems the kernel does not cache the stat
> information from one request for further requests. But the same setup
> works fine on a local file system. So it seems that glusterFS and/or
> FUSE is not able to communicate with the kernel (stat) cache. Is this
> right? And is this problem solvable?
>
> Here is some schematic diagram of our approach:
> request -> lighttpd -> Threaded FastCGI program, that does only a stat
> (via fopen) -> lighttpd opens the file for reading and writes the date
> to the socket
>
>
> In a local scenario the second open uses the cached stat and so it
> does not block other reads in lighty at that point. but with a
> glusterFS mount it still blocks there.
>
> Maybe you can give me some advice. Thank you!
>
> Bernhard J. M. Grün
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@xxxxxxxxxx
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>


[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux