[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lustre-discuss
Subject:    [Lustre-discuss] Hotspots
From:       cliffw () whamcloud ! com (Cliff White)
Date:       2011-09-21 21:57:10
Message-ID: CAGgoGxOHS1QCun+BnXG9aQ2mELZ8LXGGHQX3oLDxJKHXdEC4QA () mail ! gmail ! com
[Download RAW message or body]

Well, this is why Lustre uses striping - however if your file is very small,
it will be located on
one stripe only, and at that point it's limited by hardware.
In current Lustre (1.8.6-wc1) you can enable caching on the OSS which may
help.
cliffw


On Wed, Sep 21, 2011 at 1:16 PM, Michael Di Domenico <mdidomenico4 at gmail.com
> wrote:

> is there an easy way to identify such hotspots?
> 
> On Fri, Sep 16, 2011 at 2:24 AM, Mark Day <mark.day at rsp.com.au> wrote:
> > Hi all,
> > 
> > Does anyone have tips on dealing with 'hotspots' in a Lustre
> > filesystems? We've recently noticed some large loads caused by a large
> > number of clients hitting a single 'small' file at the same time.
> > Something like a NetApp FlexCache would seem to be a solution for this
> > but that's obviously proprietary.
> > 
> > We're currently using 1.8.3
> > 
> > tia, Mark.
> > --
> > mark day
> > _______________________________________________
> > Lustre-discuss mailing list
> > Lustre-discuss at lists.lustre.org
> > http://lists.lustre.org/mailman/listinfo/lustre-discuss
> > 
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
> 



-- 
cliffw
Support Guy
WhamCloud, Inc.
www.whamcloud.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-discuss-lustre.org/attachments/20110921/0f991b2a/attachment.htm>



[prev in list] [next in list] [prev in thread] [next in thread]