From: Peter Zaitsev <peter@mysql.com>
To: linux-kernel@vger.kernel.org
Cc: alexeyk@mysql.com
Subject: DBT2-MySQL Benchmark. "hugemem" vs "smp" kernels
Date: Mon, 12 Jul 2004 17:07:10 -0700 [thread overview]
Message-ID: <1089677229.15336.693.camel@abyss.home> (raw)
Hi,
Some half a year ago I wrote about my experience of performance of
"hugemem" vs "sm" kernels for 2.4.21-9.EL kernel from RH AS 3.0
The results I got previously were
smp hugemem
IO BOUND: 1450TPM 1250TPM
CPU BOUND: 7000TPM 4500TPM
Results are in Transactions per Minute.
This was significant regression and it was some kind of expected.
The results with newer kernel 2.4.21-15.EL are very strange however:
smp hugemem
IO BOUND: 1150TPM 1650TPM
CPU BOUND: 6300TPM 5000TPM
Well I'm pretty happy to see "hugemem" kernel improved a lot, but
what happened with SMP kernel ? Why it is slow now for IO bound case
and why it became slower than 2.4.21-9.EL ?
I'm using 4*Pentium Xeon 2.0Ghz w HT, 4GB RAM, 3WARE RAID10, EXT3
--
Peter Zaitsev, Senior Support Engineer
MySQL AB, www.mysql.com
reply other threads:[~2004-07-13 0:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1089677229.15336.693.camel@abyss.home \
--to=peter@mysql.com \
--cc=alexeyk@mysql.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
all inboxes | Powered by JetHome®