From: "Rob Mueller" <robm@fastmail.fm>
To: <linux-kernel@vger.kernel.org>
Cc: "Joseph D. Wagner" <wagnerjd@prodigy.net>,
"Jeremy Howard" <jhoward@fastmail.fm>
Subject: Re: Strange load spikes on 2.4.19 kernel
Date: Sat, 12 Oct 2002 16:54:14 +1000 [thread overview]
Message-ID: <101101c271bc$2eebf080$1900a8c0@lifebook> (raw)
In-Reply-To: 001401c2719b$9d45c4a0$53241c43@joe
> 1) If you don't need to know when a file was last accessed, mount the
> ext3 file system with the -noatime option. This disables updating of
> the "Last Accessed On:" property, which should significantly increase
> throughput.
Yes, already did that. Should have noted our fstab entry:
/dev/sda2 / ext3 defaults,noatime 1 1
> /sbin/elvtune -r 16384 -w 8192 /dev/mount-point
> where mount-point is the partition (e.g. /dev/hda5)
Thanks, we'll give this a try. Didn't know about this one before.
> 3) If the above don't work, double the journal size.
As you noted, we seem to be doing more reads than writes, so I'd be suprised
if 192M wasn't enough...
> P.S. You'd probably get more help from the ext3 mailing list.
I wasn't too sure that it was an I/O problem, which is why I posted here. As
the vmstat output showed, there didn't seem to be any sudden excessive I/O
occuring, but the load would jump enormously.
Maybe we should definitely try some different journaling modes, or disabling
journalling all together, to test if that is the actual culprit...
Rob
PS. I forgot to include the uptime dump in my last post. I just wanted to
show how spikey it was. Basically there's a long falling off decay, and then
a sudden spike again... which decays off... and then spikes again...
basically repeat what you see below over and over and over in 5-10 minute
intervals...
1:29am up 23:50, 3 users, load average: 0.35, 2.49, 2.73
1:29am up 23:51, 2 users, load average: 0.45, 2.44, 2.71
1:29am up 23:51, 2 users, load average: 0.70, 2.42, 2.71
1:29am up 23:51, 2 users, load average: 0.59, 2.34, 2.68
1:29am up 23:51, 2 users, load average: 0.58, 2.28, 2.65
1:29am up 23:51, 2 users, load average: 0.49, 2.21, 2.62
1:30am up 23:51, 2 users, load average: 0.49, 2.15, 2.60
1:30am up 23:52, 2 users, load average: 21.39, 6.43, 3.98
1:30am up 23:52, 2 users, load average: 18.10, 6.22, 3.94
1:30am up 23:52, 2 users, load average: 15.32, 6.01, 3.89
1:30am up 23:52, 2 users, load average: 13.04, 5.83, 3.86
1:30am up 23:52, 2 users, load average: 11.03, 5.64, 3.81
1:31am up 23:52, 2 users, load average: 9.41, 5.47, 3.78
1:31am up 23:53, 2 users, load average: 7.96, 5.29, 3.74
1:31am up 23:53, 2 users, load average: 6.81, 5.13, 3.70
1:31am up 23:53, 2 users, load average: 5.76, 4.96, 3.66
1:31am up 23:53, 2 users, load average: 4.88, 4.80, 3.62
1:31am up 23:53, 2 users, load average: 4.13, 4.64, 3.58
1:32am up 23:53, 2 users, load average: 3.49, 4.48, 3.54
1:32am up 23:54, 2 users, load average: 2.95, 4.34, 3.51
1:32am up 23:54, 2 users, load average: 2.50, 4.19, 3.47
1:32am up 23:54, 2 users, load average: 2.12, 4.05, 3.43
1:32am up 23:54, 2 users, load average: 1.79, 3.92, 3.39
1:32am up 23:54, 2 users, load average: 1.51, 3.79, 3.36
1:33am up 23:54, 2 users, load average: 1.43, 3.70, 3.33
1:33am up 23:55, 2 users, load average: 1.21, 3.58, 3.30
1:33am up 23:55, 2 users, load average: 1.03, 3.46, 3.26
1:33am up 23:55, 2 users, load average: 1.03, 3.38, 3.23
1:33am up 23:55, 2 users, load average: 0.87, 3.27, 3.20
1:33am up 23:55, 2 users, load average: 0.82, 3.17, 3.17
next parent reply other threads:[~2002-10-12 6:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001401c2719b$9d45c4a0$53241c43@joe>
2002-10-12 6:54 ` Rob Mueller [this message]
2002-12-11 22:54 Strange load spikes on 2.4.19 kernel Steven Roussey
2002-12-11 23:09 ` Andrew Morton
2002-12-11 23:54 ` Steven Roussey
2002-12-12 0:13 ` Andrew Morton
2002-12-12 0:31 ` Steven Roussey
[not found] <113001c27282$93955eb0$1900a8c0@lifebook.suse.lists.linux.kernel>
[not found] ` <000001c27286$6ab6bc60$7443f4d1@joe.suse.lists.linux.kernel>
[not found] ` <20021013.000127.43007739.davem@redhat.com.suse.lists.linux.kernel>
2002-10-13 7:24 ` Andi Kleen
2002-10-13 7:21 ` David S. Miller
2002-10-13 11:47 ` Hugh Dickins
2002-10-13 18:29 ` Andrew Morton
[not found] <Pine.LNX.4.33.0210130202070.17395-100000@coffee.psychology.mcmaster.ca>
2002-10-13 6:34 ` Rob Mueller
2002-10-13 7:01 ` Joseph D. Wagner
2002-10-13 7:01 ` David S. Miller
2002-10-13 7:49 ` Joseph D. Wagner
2002-10-13 7:50 ` David S. Miller
2002-10-13 8:16 ` Joseph D. Wagner
2002-10-13 8:13 ` David S. Miller
2002-10-13 8:40 ` Joseph D. Wagner
2002-10-13 8:45 ` David S. Miller
2002-10-13 8:48 ` Mike Galbraith
2002-10-13 8:48 ` David S. Miller
2002-10-13 8:51 ` William Lee Irwin III
2002-10-13 10:20 ` Ingo Molnar
2002-10-13 19:42 ` Rik van Riel
2002-10-16 21:00 ` Bill Davidsen
2002-10-13 8:59 ` Anton Blanchard
2002-10-13 9:26 ` William Lee Irwin III
2002-10-13 12:31 ` Marius Gedminas
[not found] <Pine.LNX.4.33.0210121605490.16179-100000@coffee.psychology.mcmaster.ca>
2002-10-13 0:49 ` Rob Mueller
-- strict thread matches above, loose matches on Subject: below --
2002-10-12 3:13 Joseph D. Wagner
2002-10-12 3:10 Joseph D. Wagner
2002-10-12 1:12 Rob Mueller
2002-10-12 1:25 ` Andrew Morton
2002-10-12 2:25 ` Rob Mueller
2002-10-12 3:07 ` Andrew Morton
2002-10-12 6:37 ` Rob Mueller
2002-10-12 6:44 ` Andrew Morton
2002-10-12 6:52 ` Rob Mueller
2002-10-12 7:00 ` Andrew Morton
2002-10-13 6:14 ` Rob Mueller
2002-10-13 7:27 ` Simon Kirby
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='101101c271bc$2eebf080$1900a8c0@lifebook' \
--to=robm@fastmail.fm \
--cc=jhoward@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=wagnerjd@prodigy.net \
/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