mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ralf Gross <rg@stz-softwaretechnik.com>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org, fengguang.wu@intel.com
Subject: Re: io-scheduler tuning for better read/write ratio
Date: Thu, 25 Jun 2009 09:27:54 +0200	[thread overview]
Message-ID: <20090625072754.GC16642@p15145560.pureserver.info> (raw)
In-Reply-To: <200906241057.41227.a1426z@gawab.com>

Al Boldi schrieb:
> Ralf Gross wrote:
> > The main problem is with bacula. It reads/writes from/to two
> > spoolfiles on the same device.
> >
> > I get the same behavior with 2 dd processes, one reading from disk, one
> > writing to it.
> >
> > Here's the output from dstat (5 sec intervall).
> >
> > --dsk/md1--
> > _read _writ
> >   26M   95M
> >   31M   96M
> >   20M   85M
> >   31M  108M
> >   28M   89M
> >   24M   95M
> >   26M   79M
> >   32M  115M
> >   50M   74M
> >  129M   15k
> >  147M 1638B
> >  147M    0
> >  147M    0
> >  113M    0
> >
> >
> > At the end I stopped the dd process that is writing to the device, so you
> > can see that the md device is capable of reading with >120 MB/s.
> >
> > I did this with these two commands.
> >
> > dd if=/dev/zero of=test bs=1MB
> > dd if=/dev/md1 of=/dev/null bs=1M
> 
> Try changing /proc/sys/vm/dirty_ratio = 1

$cat /proc/sys/vm/dirty_ratio
1


$dstat -D md1 -d 5
--dsk/md1--
_read _writ
  18M   18M
   0     0 
 820k  101M
  18M  113M
  26M   73M
  26M  110M
  32M  100M
  19M  111M
  13M  117M
  13M  142M
  32M   88M
  26M   99M
  38M   58M

No change. Even setting dirty_ratio to 100 didn't show any difference.


With the cfq scheduler and slice_idle = 24 (trial and error) I get better
results. Itried this before, but the overall throughput was a bit lower than
with deadline.

It seems that I can not tune deadline to get the samet behaviour.

--dsk/md1--
_read _writ
  18M   18M
  25M   77M
  51M   65M
  51M   47M
  62M   45M
  53M   28M
  45M   43M
  46M   47M
  47M   42M
  51M   41M
  38M   51M
  51M   40M
  45M   40M
  58M   42M
  69M   41M
  72M   42M
 122M    0
 141M  340k
--dsk/md1--
_read _writ
 139M  562k
 136M    0
 141M   13k
  64M    0
1638B  104M
   0   110M
   0   122M
   0   104M
   0   108M

The last numbers are for reading/writing only.

Ralf

  parent reply	other threads:[~2009-06-25  7:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 15:43 Ralf Gross
2009-06-16 16:41 ` David Newall
2009-06-16 18:40   ` Ralf Gross
2009-06-16 18:43     ` Casey Dahlin
2009-06-16 18:56       ` Ralf Gross
2009-06-16 20:16         ` Jeff Moyer
2009-06-22 14:43           ` Jeff Moyer
2009-06-22 16:31             ` Ralf Gross
2009-06-22 19:42               ` Jeff Moyer
2009-06-23  7:24                 ` Ralf Gross
2009-06-23 13:53                   ` Jeff Moyer
2009-06-24  7:25                     ` Ralf Gross
2009-06-24  7:57                       ` Al Boldi
2009-06-25  7:26                         ` Ralf Gross
2009-06-25 13:45                           ` Al Boldi
2009-06-25  7:27                         ` Ralf Gross [this message]
2009-06-26  2:19                 ` Wu Fengguang
2009-06-26 10:44                   ` Jens Axboe
2009-06-27  3:46                     ` Wu Fengguang
2009-06-29  9:47                       ` Ralf Gross

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=20090625072754.GC16642@p15145560.pureserver.info \
    --to=rg@stz-softwaretechnik.com \
    --cc=a1426z@gawab.com \
    --cc=fengguang.wu@intel.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

all inboxes | Powered by JetHome®