| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: observed significant performance improvement using "delaylog" in a real-world application |
| From: | Peter Niemayer <niemayer@xxxxxx> |
| Date: | Wed, 11 Aug 2010 20:08:33 +0200 |
| In-reply-to: | <20100811000854.GL26402@dastard> |
| References: | <i3rt4t$46c$1@xxxxxxxxxxxxxxx> <20100811000854.GL26402@dastard> |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 |
On 08/11/2010 02:08 AM, Dave Chinner wrote: One thing that you might want to try to further improve performance is the logbsize=262144 option as well. That will help flush log IO faster by doing less IOs. Tried that - but this did not have a positive effect. (In fact a slightly negative one, but that could be within the measurement accuracy). Also, if your workload is doing lots of fsync calls, then the optimisations I posted a few days ago should also help improve delaylog throughput. We don't to any fsync's. Regards, Peter Niemayer |
| Previous by Date: | Re: observed significant performance improvement using "delaylog" in a real-world application, Peter Niemayer |
|---|---|
| Next by Date: | Re: observed significant performance improvement using "delaylog" in a real-world application, Michael Monnerie |
| Previous by Thread: | Re: observed significant performance improvement using "delaylog" in a real-world application, Dave Chinner |
| Next by Thread: | Re: observed significant performance improvement using "delaylog" in a real-world application, Michael Monnerie |
| Indexes: | [Date] [Thread] [Top] [All Lists] |