public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 10846] Slow write on LSISAS1068E (SAS6/iR) on kernel >= 2.6.22
Date: Tue,  3 Jun 2008 13:15:34 -0700 (PDT)	[thread overview]
Message-ID: <20080603201534.BE46411D109@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-10846-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=10846





------- Comment #7 from anonymous@kernel-bugs.osdl.org  2008-06-03 13:15 -------
Reply-To: James.Bottomley@HansenPartnership.com

On Tue, 2008-06-03 at 09:09 -0700, bugme-daemon@bugzilla.kernel.org
wrote: 
> Should we consider, that such a difference is normal. You suggest that before
> the kernel was dangerous at writing data?

It's caching too much streaming data, yes.  The danger is largely the
amount of data you lose on a crash and mismanagement of the cache
starving other applications. It's not that much of a problem.  At an
estimated write speed of ~70MB/s your 1GB of data is only around 15s to
effect a full writeout.

> So unpacking linux kernel (for example) is 5x times slower and it is not a
> problem. That's just new way of caching data? We seldom see crashes (thanks to
> linux) and we have power supply.

There are many factors that could account for that.

> I'd like testing on same hardware windows to see its behaviour and speed.
> Anyway thanks for the clarifying of cache: write through. As you say, it was
> not evident. 
> 
> So, now, what can we do to keep 2.6.21 behaviour? That's for a mail system
> writing lots of little files and performance matters too.

Well, initially, I'd try a benchmark that simulates the actual problem,
like postmark.  A streaming write tells you very little about the entire
system performance under a mail server type load.

James


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

  parent reply	other threads:[~2008-06-03 20:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 14:57 [Bug 10846] New: Slow write on LSISAS1068E (SAS6/iR) on kernel >= 2.6.22 bugme-daemon
2008-06-02 15:11 ` James Bottomley
2008-06-02 15:11 ` [Bug 10846] " bugme-daemon
2008-06-02 21:09 ` bugme-daemon
2008-06-03  7:00 ` bugme-daemon
2008-06-03 14:11   ` James Bottomley
2008-06-03 14:12 ` bugme-daemon
2008-06-03 16:09 ` bugme-daemon
2008-06-03 20:15   ` James Bottomley
2008-06-03 19:21 ` bugme-daemon
2008-06-03 20:15 ` bugme-daemon [this message]
2008-06-04 15:22 ` bugme-daemon
2008-06-13  7:52 ` bugme-daemon

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=20080603201534.BE46411D109@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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