| To: | Richard Ems <richard.ems@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS unlink still slow on 3.1.9 kernel ? |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 14 Feb 2012 14:43:06 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <4F3A2DE9.5050901@xxxxxxxxxxxxxxxxx> |
| References: | <20120213171556.GA13449@xxxxxxxxxxxxx> <4F3947D6.5060402@xxxxxxxxxxxxxxxxx> <20120213172937.GA25248@xxxxxxxxxxxxx> <4F394E10.9000804@xxxxxxxxxxxxxxxxx> <20120213180220.GA24163@xxxxxxxxxxxxx> <4F395134.8030202@xxxxxxxxxxxxxxxxx> <20120213181012.GA27962@xxxxxxxxxxxxx> <4F395B1A.7010709@xxxxxxxxxxxxxxxxx> <20120213211654.GA20192@xxxxxxxxxxxxx> <4F3A2DE9.5050901@xxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Tue, Feb 14, 2012 at 10:48:25AM +0100, Richard Ems wrote: > It didn't improve, 100 min again. > > > > >> Or will only unlink run time improve ? > > > > Yes. > > rm took about 110 min. In that case you're pretty much bound by the time the directory traversals help. Using larger inodes will help you as we won't have to seek for the external attribute block. Not filling a fs 100% will probably help by reducing the fragmentaion, as will using larger directory blocks as suggested by Dave. A patch to improve the unlink path won't help the traversal speed ever, though. |
| Previous by Date: | Re: XFS unlink still slow on 3.1.9 kernel ?, Christoph Hellwig |
|---|---|
| Next by Date: | Re: XFS unlink still slow on 3.1.9 kernel ?, Christoph Hellwig |
| Previous by Thread: | Re: XFS unlink still slow on 3.1.9 kernel ?, Richard Ems |
| Next by Thread: | Re: XFS unlink still slow on 3.1.9 kernel ?, Richard Ems |
| Indexes: | [Date] [Thread] [Top] [All Lists] |