From: Chris Mason <chris.mason@oracle.com>
To: Brice Figureau <brice+lklm@daysofwonder.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Sluggish system while copying large files.
Date: Mon, 23 Oct 2006 07:29:20 -0400 [thread overview]
Message-ID: <20061023112920.GA5560@think.oraclecorp.com> (raw)
In-Reply-To: <1161596405.473.29.camel@localhost.localdomain>
On Mon, Oct 23, 2006 at 11:40:05AM +0200, Brice Figureau wrote:
>
> I'll try the data=writeback mount option. Is it possible to remount the
> partition and change the journal option on a running system?
Not with ext3, sorry.
>
> > Since mysql is probably triggering tons of fsyncs or O_SYNC writes,
> > you may want to increase the size of the ext3 log.
>
> Mysql is using O_DIRECT for its datafile. I don't know how it relates to
> the sync things, but I guess that to be truly ACID, it has to fsync the
> files on each transactions.
> How can I increase the ext3 log ?
> Any idea of the size I should use (and what is the default) ?
Even when using O_DIRECT, if the file is extended an FS commit is
triggered to record the extension.
>
> > If mysql is constantly appending to the files holding your tables, the
> > synchronous writes are more expensive and log intensive. Check your
> > setup to see if you can manually extend any of those files to avoid
> > constantly growing table files.
>
> The use of a battery-backed RAID cache should mitigate the sync writes,
> and since our mysql load is quite low, the machine shouldn't definitely
> freeze for seconds while copying files.
Ok, I would start with only doing data=writeback. That is probably a
big part of the problem.
-chris
prev parent reply other threads:[~2006-10-23 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 13:56 Sluggish system while copying large files Brice Figureau
2006-10-13 14:14 ` Paolo Ornati
2006-10-18 15:09 ` Chris Mason
2006-10-23 9:40 ` Brice Figureau
2006-10-23 11:29 ` Chris Mason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061023112920.GA5560@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=brice+lklm@daysofwonder.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox