| To: | Linux fs XFS <xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?) |
| From: | Stefan Ring <stefanrin@xxxxxxxxx> |
| Date: | Fri, 6 Apr 2012 09:27:19 +0200 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=b5Jk7X7X+13HmtHR3YPEl91j4gyTwxhcahOtGHwZkZQ=; b=SHwogRY5oEfoS0/M4VCB15bicRcBRSseEBy4G4pHkxt1tnBLyfg9g9lRnALZLKNPVt GoLUqJu31uHTd+1pxZjqi2UoUE53xnOYkDjXLAPbMAzbrTK3FTZOCahNZfggCNk4BdjB 9hvoPhOlUtulGwI6rW5cbHp4pV3vA7ET/qlCeQfzWY5lR8RIVTwx/GGoIsf1juc0NM4C bsP7isLh4zW5u52RRnnJ4cWopLkBzF6gsgHee9Beb9PASsdoNXUHy1p1m61vmokvoOQw Y+dm0F04z7pFEAgZJQSAVnCLXXl+CrtHVTO0psIh5tcgjaTCyMltv/hWjwsV2d7rif2t QCwQ== |
| In-reply-to: | <20350.13616.901974.523140@xxxxxxxxxxxxxxxxxx> |
| References: | <CAAxjCEwBMbd0x7WQmFELM8JyFu6Kv_b+KDe3XFqJE6shfSAfyQ@xxxxxxxxxxxxxx> <20350.9643.379841.771496@xxxxxxxxxxxxxxxxxx> <20350.13616.901974.523140@xxxxxxxxxxxxxxxxxx> |
> As to this, in theory even having split the files among 4 AGs, > the upload from system RAM to host adapter RAM and then to disk > could happen by writing first all the dirty blocks for one AG, > then a long seek to the next AG, and so on, and the additional > cost of 3 long seeks would be negligible. Yes, that’s exactly what I had in mind, and what prompted me to write this post. It would be about 10 times as fast. That’s what bothers me so much. |
| Previous by Date: | Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Stefan Ring |
|---|---|
| Next by Date: | Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Stefan Ring |
| Previous by Thread: | Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Peter Grandi |
| Next by Thread: | Re: XFS: Abysmal write performance because of excessive seeking (allocation groups to blame?), Stan Hoeppner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |