public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: linux-kernel@vger.kernel.org
Subject: Linux I/O scheduling - ionice & co
Date: Fri, 28 Apr 2006 22:45:06 +0200	[thread overview]
Message-ID: <1092993727@web.de> (raw)

Hello experts!

Whenever I do large file operations on my VMware GSX Server (copying/backup operations on the HOST), all the VMs become dead slow, regardless what elevator i select at boot time.
 
what can I do that dedicated processes get higher preference regarding I/O ?
 
from this list i found, that in recent kernels we have cfq/ionice for this.
is this rated "stable" and does it already work well?
 
maybe there are alternative approaches for this?
 
let me give another example:
 
if i start an I/O hog like "dd if=/dev/zero of=test.dat" the whole interactivity of a linux system is being influenced very negatively. i have found that working on a system running an I/O hog often becomes a real pain.
if i start an CPU hog or syscall hog like "while true;do true;done" or "while /bin/true;do /bin/true;done" this never has such bad effects than starting an I/O hog.
 
is it possible to adress this by some more "fine-tuning" or is this just because of the "nature" of I/O scheduling ?
 
i would be happy if somebody could give a comment or share his experience about this.
 
TIA
roland k.
systems engineer
 
ps:
no comment about the behaviour of a windows system which is under high I/O load..... ;)
 
 
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192


             reply	other threads:[~2006-04-28 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 20:45 devzero [this message]
2006-04-28 23:53 ` Linux I/O scheduling - ionice & co Con Kolivas

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=1092993727@web.de \
    --to=devzero@web.de \
    --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