gluster-devel
[Top][All Lists]
Advanced

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

Re: [Gluster-devel] Handling huge number of file read requests


From: Sebastien LELIEVRE
Subject: Re: [Gluster-devel] Handling huge number of file read requests
Date: Fri, 04 May 2007 16:21:28 +0200
User-agent: Thunderbird 1.5.0.10 (X11/20060911)

I think Amrik is planning to use glusterfs, and describes the problem he
is experiencing with his current cluster (filesystem) configuration.

But I may have misunderstood

Sebastien.

Anand Avati a écrit :
> Amrik,
>  can you send me your config files of both server and client?
> 
> regards,
> avati
> 
> On 5/4/07, Amrik Singh <address@hidden> wrote:
>> Hi Guys,
>>
>> We are hoping that glusterfs would help us in the particular problem
>> that we are facing with our cluster. We have a visual search application
>> that runs on a cluster with around 300 processors. These compute nodes
>> run a search for images that are hosted on an NFS server. In certain
>> circumstances all these compute nodes are sending requests for query
>> images at extremely high rates (20-40 images per second). When 300 nodes
>> send 20-40 requests per second for these images, the NFS server just
>> can't cope with it and we start seeing a lot of retransmissions and a
>> very high wait time on the server as well as on the nodes. The images
>> are sized at around 2MB each.
>>
>> With the current application we are not in a position where we can
>> quickly change the way things are being done so we are looking for a
>> file system that can handle this kind of situation. We tried glusterfs
>> with the default settings but we did not see any improvement. Is there a
>> way to tune glusterfs to handle this kind of situation.
>>
>> I can provide more details about our setup as needed.
>>
>>
>> thanks
>>
>> -- 
>> Amrik Singh
>> Idée Inc.
>> http://www.ideeinc.com
>>

Sebastien LELIEVRE
address@hidden           Services to ISP
TBS-internet                   http://www.TBS-internet.com/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]