All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Russell Coker <russell@coker.com.au>
Cc: "Sewell, Cassandra D   (Cassandra)" <csewell@avaya.com>,
	reiserfs-list@namesys.com
Subject: Re: 2.4.20 at kernel.org and data logging
Date: 18 Jan 2003 10:57:11 -0500	[thread overview]
Message-ID: <1042905430.31095.2343.camel@tiny.suse.com> (raw)
In-Reply-To: <200301181125.16752.russell@coker.com.au>

On Sat, 2003-01-18 at 05:25, Russell Coker wrote:
> On Fri, 17 Jan 2003 00:51, Sewell, Cassandra D (Cassandra) wrote:
> > Is the data logging patch for 2.4.20 kernel considered
> > complete?  I see a patch at
> > ftp.suse.com/pub/people/mason/patches/data-logging/2.4.20.  Also will this
> > patch be considered working for the last stable 2.4.20 posted at the
> > kernel.org location?
> >
> > I am in the process of upgrading some machines from 2.2.x (I know way
> > overdue), and need the data-logging capability.
> 
> I am using those patches on some 2.4.20 machines running as Qmail mail 
> servers.  I have the /var file system mounted with data journalling.
> 
> I have 4 machines running each with >250,000 mail boxes with continual heavy 
> IO load (the load never goes below 100 disk writes per second).
> 
> I found the benefit to be much smaller than I had hoped.  The patches in 
> question have a number of other performance improvements which made a huge 
> and noticable difference.  data=journal seemed to make a small difference, 
> but nothing exciting.

The benefit from data=journal varies largely by the size of the files in
use.  But Russell, you might be hitting other bottlenecks having to do
with reading the directory items off disk (that many directories means
lots of inode).  

Also, we should probably try switching you to a highmem io enabled
kernel, I'm almost done with a patch to put the 2.4.21 data logging code
in the -aa kernel.

-chris



  reply	other threads:[~2003-01-18 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 23:51 2.4.20 at kernel.org and data logging Sewell, Cassandra D (Cassandra)
2003-01-17  0:33 ` Manuel Krause
2003-01-18 10:25 ` Russell Coker
2003-01-18 15:57   ` Chris Mason [this message]
2003-01-19 10:45     ` Russell Coker
2003-01-23 23:10     ` slightly [OT] highmem (was Re: 2.4.20 at kernel.org and data logging) Manuel Krause
2003-01-23 23:40       ` Russell Coker
2003-01-24  0:18         ` Manuel Krause
2003-01-24  0:24           ` Russell Coker
2003-01-24  7:50           ` Oleg Drokin
2003-01-24 17:00             ` Dieter Nützel
2003-01-24 17:03               ` Oleg Drokin
2003-01-24 17:15                 ` Dieter Nützel

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=1042905430.31095.2343.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=csewell@avaya.com \
    --cc=reiserfs-list@namesys.com \
    --cc=russell@coker.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.