From: Tim Moore <linux-raid@nsr500.net>
To: linux-raid@vger.kernel.org
Subject: Re: raid5 performance after upgrade to 2.4.28
Date: Thu, 13 Jan 2005 08:25:40 -0800 [thread overview]
Message-ID: <41E6A104.4080608@nsr500.net> (raw)
Did values change in /proc/sys/vm/{min,max}-readahead?
http://lists.us.dell.com/pipermail/linux-poweredge/2004-February/036166.html
Guy wrote:
> Now the bad news...
>
> I have 2 CPUs P3-500Mhz, 512Meg ram. So I ran 2 bonnies at the same time.
>
> Kernel 2.4.20-8 with 2 Bonnies at the same time:
> Version 1.03 ------Sequential Output------ --Sequential Input- --Random-
> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
> Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
> watkins-ho 1G 3091 85 18593 44 9733 24 3443 97 59895 60 249.6 6
> watkins-ho 1G 2980 87 21176 54 10167 23 3478 99 44525 44 384.2 9
> ---- ----- ----- ---- ------ -----
> Total 6071 39769 19900 6921 104420 633.8
>
> Kernel 2.4.28 with 2 Bonnies at the same time:
> watkins-ho 1G 4456 92 17922 52 6489 17 4961 96 26571 32 320.4 12
> watkins-ho 1G 4343 89 17987 52 6197 17 4946 96 25646 31 363.7 7
> ---- ----- ----- ---- ------ -----
> Total 8799 35909 12686 9907 52217 684.1
>
> Very odd, the sequential read speed is almost exactly 1/2 now.
>
> Oh well, I still can't tell without a tool to measure the speed.
> But I still don't like it!
>
> My network is only 100BaseT, so it is still well beyond that!
>
> Guy
>
> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org
> [mailto:linux-raid-owner@vger.kernel.org] On Behalf Of Guy
> Sent: Wednesday, January 12, 2005 1:17 AM
> To: linux-raid@vger.kernel.org
> Subject: raid5 performance after upgrade to 2.4.28
>
> About 1 month ago I upgraded from Kernel 2.4.20-8 to 2.4.28.
> Today I noticed my sequential read speed is up by about 12%.
>
> I don't recall making any other changes that would affect speed.
> So, I guess the Kernel upgrade made the difference.
>
> An old bonnie output:
> Version 1.03 ------Sequential Output------ --Sequential Input- --Random-
> -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
> Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP
> watkins-ho 1G 3293 97 34587 89 22306 53 3549 99 67492 63 500.1 9
>
> Today:
> watkins-ho 1G 4944 99 31719 65 18538 43 5184 98 75440 71 602.5 8
> ^^^^ ^^^^ ^^^^^ ^^^^^
>
> Some things improved, others decreased.
>
> Of course, no change I can notice on my own.
> I needed to measure performance to notice.
>
> I guess I should try Kernel 2.6 some day.
>
> Guy
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
| for direct mail add "private_" in front of user name
next reply other threads:[~2005-01-13 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 16:25 Tim Moore [this message]
2005-01-13 16:45 ` raid5 performance after upgrade to 2.4.28 Guy
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 5:18 raid5 performance - 2.4.28 Tim Moore
2005-01-12 6:17 ` raid5 performance after upgrade to 2.4.28 Guy
2005-01-12 7:44 ` Guy
2005-01-13 16:24 ` Tim Moore
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=41E6A104.4080608@nsr500.net \
--to=linux-raid@nsr500.net \
--cc=linux-raid@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 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.