|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|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:188.8.131.52) 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
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:|
|Next by Date:|
|Previous by Thread:|
|Next by Thread:|
|Indexes:||[Date] [Thread] [Top] [All Lists]|