From: Andrew Morton <akpm@zip.com.au>
To: "Griffiths, Richard A" <richard.a.griffiths@intel.com>
Cc: "'Jens Axboe'" <axboe@suse.de>,
mgross@unix-os.sc.intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lse-tech@lists.sourceforge.net
Subject: Re: ext3 performance bottleneck as the number of spindles gets large
Date: Thu, 20 Jun 2002 13:18:40 -0700 [thread overview]
Message-ID: <3D1238A0.EA4906FB@zip.com.au> (raw)
In-Reply-To: 01BDB7EEF8D4D3119D95009027AE99951B0E63E4@fmsmsx33.fm.intel.com
"Griffiths, Richard A" wrote:
>
> We ran without highmem enabled so the Kernel only saw 1GB of memory.
>
Yup. I take it back - high ext3 lock contention happens on 2.5
as well, which has block-highmem. With heavy write traffic onto
six disks, two controllers, six filesystems, four CPUs the machine
spends about 40% of the time spinning on locks in fs/ext3/inode.c
You're un dual CPU, so the contention is less.
Not very nice. But given that the longest spin time was some
tens of milliseconds, with the average much lower, it shouldn't
affect overall I/O throughput.
Possibly something else is happening. Have you tested ext2?
next prev parent reply other threads:[~2002-06-20 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 15:26 ext3 performance bottleneck as the number of spindles gets la rge Griffiths, Richard A
2002-06-20 20:18 ` Andrew Morton [this message]
2002-06-20 18:08 ` ext3 performance bottleneck as the number of spindles gets large mgross
2002-06-20 21:25 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 21:50 ext3 performance bottleneck as the number of spindles gets la rge Griffiths, Richard A
2002-06-21 7:58 ` ext3 performance bottleneck as the number of spindles gets large Andrew Morton
2002-06-21 18:46 ` mgross
2002-06-21 19:26 ` Chris Mason
2002-06-21 19:56 ` Andrew Morton
2002-06-23 4:02 ` Christopher E. Brown
2002-06-23 4:33 ` Andreas Dilger
2002-06-23 6:00 ` Christopher E. Brown
2002-06-19 21:29 mgross
2002-06-20 0:54 ` Andrew Morton
2002-06-20 9:54 ` Stephen C. Tweedie
2002-06-20 1:55 ` Andrew Morton
2002-06-20 6:05 ` Jens Axboe
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=3D1238A0.EA4906FB@zip.com.au \
--to=akpm@zip.com.au \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mgross@unix-os.sc.intel.com \
--cc=richard.a.griffiths@intel.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