From: Andrew Lutomirski <andy@luto.us>
To: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: 2.6.37: Multi-second I/O latency while untarring
Date: Fri, 11 Feb 2011 10:08:52 -0500 [thread overview]
Message-ID: <AANLkTin4628kHMRogoAarDWyGGb8-6-BiixihJmy_AUj@mail.gmail.com> (raw)
As I type this, I have an ssh process running that's dumping data into
a fifo at high speed (maybe 500Mbps) and a tar process that's
untarring from the same fifo onto btrfs. The btrfs fs is mounted -o
space_cache,compress. This machine has 8GB ram, 8 logical cores, and
a fast (i7-2600) CPU, so it's not an issue with the machine struggling
under load.
Every few tens of seconds, my system stalls for several seconds.
These stalls cause keyboard input to be lost, firefox to hang, etc.
Setting tar's ionice priority to best effort / 7 or to idle makes no difference.
ionice idle and queue_depth = 1 on the disk (a slow 2TB WD) also makes
no difference.
max_sectors_kb = 64 in addition to the above doesn't help either.
latencytop shows regular instances of 2-7 *second* latency, variously
in sync_page, start_transaction, btrfs_start_ordered_extent, and
do_get_write_access (from jbd2 on my ext4 root partition).
echo 3 >drop_caches gave me 7 GB free RAM. I still had stalls when
4-5 GB were still free (so it shouldn't be a problem with important
pages being evicted).
In case it matters, all of my partitions are on LVM on dm-crypt, but
this machine has AES-NI so the overhead from that should be minimal.
In fact, overall CPU usage is only about 10%.
What gives? I thought this stuff was supposed to be better on modern kernels.
--Andy
next reply other threads:[~2011-02-11 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 15:08 Andrew Lutomirski [this message]
2011-02-11 15:44 ` 2.6.37: Multi-second I/O latency while untarring Chris Mason
2011-02-11 19:56 ` Andrew Lutomirski
2011-02-12 0:35 ` Andrew Lutomirski
2011-02-14 15:22 ` Chris Mason
2011-03-29 3:50 ` Andrew Lutomirski
2011-02-11 15:54 ` Matt
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=AANLkTin4628kHMRogoAarDWyGGb8-6-BiixihJmy_AUj@mail.gmail.com \
--to=andy@luto.us \
--cc=linux-btrfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).