From: Andreas Dilger <adilger@turbolabs.com>
To: "DICKENS,CARY (HP-Loveland,ex2)" <cary_dickens2@hp.com>
Cc: "'Andrew Morton'" <akpm@zip.com.au>,
"Kernel Mailing List (E-mail)" <linux-kernel@vger.kernel.org>,
"HABBINGA,ERIK (HP-Loveland,ex1)" <erik_habbinga@hp.com>
Subject: Re: Kernel performance in reference to 2.4.5pre1
Date: Thu, 18 Oct 2001 14:17:14 -0600 [thread overview]
Message-ID: <20011018141714.M1144@turbolinux.com> (raw)
In-Reply-To: <C5C45572D968D411A1B500D0B74FF4A80418D57F@xfc01.fc.hp.com>
In-Reply-To: <C5C45572D968D411A1B500D0B74FF4A80418D57F@xfc01.fc.hp.com>
Andrew Morton [mailto:akpm@zip.com.au] wrote:
> SFS is a rather specialised workload, and synchronous NFS exports
> are not a thing which gets a lot of attention. It could be one
> small, hitherto unnoticed change which caused this performance
> regression. And it appears that the change occurred between 2.4.5
> and 2.4.7.
Cary, also note that Andrew did some work with ext3 which can greatly
improve the performance of synchronous I/O. Granted, it doesn't fix
any performance issues in the VM or VFS that may have been introduced,
but if you are looking for good benchmark numbers, give ext3 a try.
Use a large journal to avoid journal flushes for sync I/O. See:
http://marc.theaimsgroup.com/?l=linux-kernel&m=99650624414465&w=4
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-10-18 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-18 19:38 Kernel performance in reference to 2.4.5pre1 DICKENS,CARY (HP-Loveland,ex2)
2001-10-18 20:17 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-18 16:38 DICKENS,CARY (HP-Loveland,ex2)
2001-10-18 18:33 ` Andrew Morton
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=20011018141714.M1144@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=akpm@zip.com.au \
--cc=cary_dickens2@hp.com \
--cc=erik_habbinga@hp.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