From: Theodore Ts'o <tytso@mit.edu>
To: "Joseph D. Wagner" <joe@josephdwagner.info>
Cc: linux-ext4@vger.kernel.org
Subject: Re: dump ext4 performance degrades linearly as disk fills
Date: Fri, 20 Jun 2014 20:38:49 -0400 [thread overview]
Message-ID: <20140621003849.GA15531@thunk.org> (raw)
In-Reply-To: <d5c373beb24a9da86986ea43afe13594@josephdwagner.info>
On Thu, Jun 19, 2014 at 11:42:38AM -0700, Joseph D. Wagner wrote:
> Hello Theo.
>
> I know you're working-for-free and have other things to do besides
> work on my low priority problem. However, I haven't heard from you.
> I just wanted to follow-up and make sure you got my attachment,
> not that anything fell through the cracks so-to-speak.
Sorry, I did get your attachment. I've just been crazy busy as of
late. Between work and several other projects, I just haven't had
time to get back to this.
Nothing really obvious is jumping out at me. There are some
tracepoints we could set to try to analyze what might be happening,
but it's going to take a bit of time to describe how to do it, and
more time to analyze the results afterwards, which is why I haven't
gotten back to you.
The short version is we'd want to enable the tracepoints
"ext4_mballoc_alloc" and "ext4_read_block_bitmap_load" and grab some
trace output at the beginning of the backup, and at the end, and see
if anything obvious shows up.
Another experiment that might be worth trying to run the backup to 30%
or so, and then stop the backup, and rename the backup file so it's
not overwritten, and then start a fresh full backup. What we would be
trying to determine is whether the decreased performance is due to the
disk space fillin gup, or due the size of the backup file that is
being written which is causing the slow down.
Cheers,
- Ted
next prev parent reply other threads:[~2014-06-21 0:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 18:42 dump ext4 performance degrades linearly as disk fills Joseph D. Wagner
2014-06-21 0:38 ` Theodore Ts'o [this message]
2014-07-29 20:55 ` Phillip Susi
2014-07-29 22:48 ` Joseph D. Wagner
-- strict thread matches above, loose matches on Subject: below --
2014-06-20 23:59 Joseph D. Wagner
2014-06-16 5:43 Joseph D. Wagner
2014-06-16 12:42 ` Theodore Ts'o
2014-06-17 14:08 ` Joseph D. Wagner
2014-06-17 14:51 ` Theodore Ts'o
2014-06-16 21:48 ` Andreas Dilger
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=20140621003849.GA15531@thunk.org \
--to=tytso@mit.edu \
--cc=joe@josephdwagner.info \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).