From: Dick Streefland <dick.streefland@altium.nl>
To: Erik Cumps <erik.cumps@esaturnus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unexpected slow block device write IO performance compared to uncached, unsynced direct IO using stock kernels
Date: Tue, 1 Sep 2015 11:15:35 +0200 [thread overview]
Message-ID: <20150901091535.GA21329@altium.nl> (raw)
In-Reply-To: <CALS80vgNzNENo=mDSt2b0363UXdgnQ6GtyActdYNs=oZgunpOg@mail.gmail.com>
On Thursday 2015-06-18 09:35, Erik Cumps wrote:
| On Tue, Jun 16, 2015 at 3:56 PM, Erik Cumps <erik.cumps@esaturnus.com> wrote:
| > The context is a 16 GB 32-bit intel debian workstation, using an ext4
| > filesystem with journalling, on a lvm SATA3 SSD disk, with relatively
| > recent stock kernels from 3.2 onwards to 4.0, running some KVM virtual
| > machines. The host system (so not the virual machines) shows sporadic
| > extremely slow write performance (around 4 megabytes per second).
| > However, if we use the debian 3.2.0 kernel this problem does not
| > manifest itself.
[...]
| Actually, it is the *synchronous*, direct IO that matches the expected
| raw write performance of the device.
|
| The "regular IO" test is doing roughly this:
|
| echo 3 > /proc/sys/vm/drop_caches
| dd if=ramdisk_file of=test_file bs=1M count=100
| dd if=ramdisk_file of=test_file bs=1M count=100
| dd if=ramdisk_file of=test_file bs=1M count=100
|
| The direct IO test is doing roughly this:
|
| echo 3 > /proc/sys/vm/drop_caches
| dd if=ramdisk_file of=test_file oflag=sync,direct bs=1M count=100
| dd if=ramdisk_file of=test_file oflag=sync,direct bs=1M count=100
| dd if=ramdisk_file of=test_file oflag=sync,direct bs=1M count=100
I'm seeing this as well here on a number of new Dell Optiplex 7020
machines and one older Optiplex 780, all with 8GB RAM and running
Ubuntu 14.04 in 32-bit mode.
A simple dd command shows the problem:
$ dd bs=1M count=10 if=/dev/zero of=/tmp/ddtest
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 7.02392 s, 1.5 MB/s
$ dd bs=1M count=10 if=/dev/zero of=/tmp/ddtest oflag=sync,direct
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.535397 s, 19.6 MB/s
In my case, running:
echo 3 > /proc/sys/vm/drop_caches
will restore the normal speed for a limited time:
$ dd bs=1M count=10 if=/dev/zero of=/tmp/ddtest
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.0123759 s, 847 MB/s
There is an old Ubuntu bug report describing the same issue:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/1333294
--
Dick
next prev parent reply other threads:[~2015-09-01 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 13:56 Erik Cumps
2015-06-18 7:35 ` Erik Cumps
2015-09-01 9:15 ` Dick Streefland [this message]
2015-09-02 14:12 ` Dick Streefland
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=20150901091535.GA21329@altium.nl \
--to=dick.streefland@altium.nl \
--cc=erik.cumps@esaturnus.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
Powered by JetHome