xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: XFS: Abysmal write performance because of excessive seeking (allocat

from [Joe Landman] [Permanent Link][Original]
To: xfs@xxxxxxxxxxx
Subject: Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?)
From: Joe Landman <joe.landman@xxxxxxxxx>
Date: Tue, 10 Apr 2012 10:32:20 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=dA8SV3m3cVbcItBBMsMI+fpZNMchJICGxAYwJRfUdLk=; b=ip7h52ZUH+w6ycPcx/b1XOsKQ1Z1DbB61vQW0ZFy2TpKKOpIVgwM8fZTYcRxK0S3z5 llgC26d3W+6VUK1cjLrpwSFaw+H0ign7V6PIqUoEQhcx1LST0spoEClAAR2W8tw1/kMe FIP+uuPZRQiqy9wVD1OqIMyyykUGPkVe3nGVQw9l66nXc2r+iteysMVOUWl3v+kviDQh 1sR5xhxUt3sSFkdVGu4Z7sa/hwmnxqAugX3x0KqX2lx0eFSOde7HqS/eL9nTy9+k7WnY U1y61ViK1erMZjOkR4WzixlYZyuQ7rkkZucqxS5swdyGFLyWUbmz8t7b6EIUlW7HR1r5 lllQ==
In-reply-to: <CAAxjCEzRa7CpbA9iESEDjmWQMsJTjkWHJj69ADOXDa4CiRpx3w@xxxxxxxxxxxxxx>
References: <CAAxjCEwBMbd0x7WQmFELM8JyFu6Kv_b+KDe3XFqJE6shfSAfyQ@xxxxxxxxxxxxxx> <20120405213740.GA22824@xxxxxxxxxxxxx> <CAAxjCExBcaB6J-u7ivZKWnKiF7oP10JRxzKzQNRuppHkTE2Tzw@xxxxxxxxxxxxxx> <201204072057.38286.Martin@xxxxxxxxxxxx> <CAAxjCEzRa7CpbA9iESEDjmWQMsJTjkWHJj69ADOXDa4CiRpx3w@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120329 Thunderbird/11.0.1 
On 04/10/2012 10:02 AM, Stefan Ring wrote:

And is XFS aligned to the RAID 6?

What does xfs_info display on it?


Yes, it’s aligned.

meta-data=/dev/mapper/vg_data-lvhome isize=256    agcount=4,
agsize=73233656 blks
          =                       sectsz=512   attr=2
data     =                       bsize=4096   blocks=292934624, imaxpct=5
          =                       sunit=8      swidth=32 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal               bsize=4096   blocks=143040, version=2
          =                       sectsz=512   sunit=8 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

I changed the stripe size to 32kb in the meantime. This way, it
performs slightly better.
try 128k to 512k for stripe size. And try to increase your agcount by (nearly) an order of magnitude. 


--
Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics Inc.
email: landman@xxxxxxxxxxxxxxxxxxxxxxx
web  : http://scalableinformatics.com
       http://scalableinformatics.com/sicluster
phone: +1 734 786 8423 x121
fax  : +1 866 888 3112
cell : +1 734 612 4615
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Stefan Ring
Next by Date:  Re: [PATCH 1/3] xfs: kill XBF_LOCK, Mark Tinguely
Previous by Thread:  Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Stefan Ring
Next by Thread:  Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Stefan Ring
Indexes:  [Date] [Thread] [Top] [All Lists]