xfs
[Top] [All Lists]

Re: inode64 workaround

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: inode64 workaround
From: Deanan <delusion@xxxxxxxxxxxx>
Date: Thu, 30 Nov 2006 12:33:35 -0800
Cc: chatz@xxxxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <456E67EB.2030008@xxxxxxxxxxx>
References: <200611290027.AA04740@xxxxxxxxxxxxxxxxxxxxxxxx> <1164838985.4992.30.camel@edge> <456E1B08.7090802@xxxxxxxxxxxx> <456E2A30.4010101@xxxxxxxxxxxxxxxxx> <456E2D0E.2000007@xxxxxxxxxxxx> <456E30A5.6080109@xxxxxxxxxxxxxxxxx> <456E35CA.2000601@xxxxxxxxxxxx> <456E67EB.2030008@xxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.8 (Windows/20061025)
It's a generic 2.6.9 kernel (AFAIK).
I tried the same setting on a different box with SLES 9 SP3 (2.6.5) which does have rotorstep.
With inode64 I can sustain 235+MB/s on the same array test after test.
When I do not mount with inode64, I get the same results as the 32bit machine (~100-130MB/s) Without inode64 plus rotorstep (set to 255), the perfomance improves to about 140-160MB/s.

Generally the first test is fast and then drops over the next few tests (even writing as few
as 100 16mb files per test).

Thanks,

Deanan

Deanan wrote:
Thanks. Unfortunately 2.6.9 doesn't have it. :(

Is this rhel4?

You could probably pretty easily add the inode rotor code into the xfs modules that you're using, if that's the case.

-Eric

This is a sysctl, see sysctl(8).

It was introduced to XFS in October 2004, I'm not sure if it made 2.6.9.

If this doesn't help a little then I'm unsure why you think that inode64 is
going to solve your problem?

David






<Prev in Thread] Current Thread [Next in Thread>