mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Knoblauch <spamtrap@knobisoft.de>
To: Chuck Ebbert <cebbert@redhat.com>, spamtrap@knobisoft.de
Cc: linux-kernel@vger.kernel.org,
	Peter zijlstra <a.p.zijlstra@chello.nl>,
	mingo@redhat.com
Subject: Re: Understanding I/O behaviour - next try
Date: Wed, 29 Aug 2007 14:43:08 -0700 (PDT)	[thread overview]
Message-ID: <856205.2054.qm@web32611.mail.mud.yahoo.com> (raw)
In-Reply-To: <46D59DE2.2070405@redhat.com>


--- Chuck Ebbert <cebbert@redhat.com> wrote:

> On 08/28/2007 11:53 AM, Martin Knoblauch wrote:
> > 
> >  The basic setup is a dual x86_64 box with 8 GB of memory. The
> DL380
> > has a HW RAID5, made from 4x72GB disks and about 100 MB write
> cache.
> > The performance of the block device with O_DIRECT is about 90
> MB/sec.
> > 
> >  The problematic behaviour comes when we are moving large files
> through
> > the system. The file usage in this case is mostly "use once" or
> > streaming. As soon as the amount of file data is larger than 7.5
> GB, we
> > see occasional unresponsiveness of the system (e.g. no more ssh
> > connections into the box) of more than 1 or 2 minutes (!) duration
> > (kernels up to 2.6.19). Load goes up, mainly due to pdflush threads
> and
> > some other poor guys being in "D" state.
> 
> Try booting with "mem=4096M", "mem=2048M", ...
> 
> 

 hmm. I tried 1024M a while ago and IIRC did not see a lot [any]
difference. But as it is no big deal, I will repeat it tomorrow.

 Just curious - what are you expecting? Why should it help?

Thanks
Martin


------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www:   http://www.knobisoft.de

  reply	other threads:[~2007-08-29 21:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-28 15:53 Martin Knoblauch
     [not found] ` <20070829013858.GA7721@mail.ustc.edu.cn>
2007-08-29  1:38   ` Fengguang Wu
2007-08-29  8:15     ` Martin Knoblauch
     [not found]       ` <20070829084039.GA32016@mail.ustc.edu.cn>
2007-08-29  8:40         ` Fengguang Wu
2007-08-29  9:22           ` Martin Knoblauch
2007-09-13 14:17       ` Peter Zijlstra
2007-08-29  9:48 ` Jens Axboe
2007-08-29 14:26   ` Martin Knoblauch
2007-08-30 10:50   ` Martin Knoblauch
2007-08-29 16:25 ` Chuck Ebbert
2007-08-29 21:43   ` Martin Knoblauch [this message]
     [not found] <fa.tV0SjP5wHRgCEzqJw2C8w4+Fh90@ifi.uio.no>
     [not found] ` <fa.NN9klzYbZhoZ+YoOWgrMeLtzlHE@ifi.uio.no>
2007-08-29 14:27   ` Robert Hancock
2007-08-30 10:26     ` Martin Knoblauch

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=856205.2054.qm@web32611.mail.mud.yahoo.com \
    --to=spamtrap@knobisoft.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    /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