From: dth@cistron.nl (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Q: why _less_ performance on machine with SMP then with UP kernel ?
Date: Tue, 13 Sep 2005 21:12:15 +0000 (UTC) [thread overview]
Message-ID: <dg7fbf$5df$1@news.cistron.nl> (raw)
I've been posting here recently bout our newsgateway.
For short:
If i enable both CPU's i get less performance than enabling both cpu's
Long version:
Here is a description of the setup:
---
It's a tyan server /motherboard
http://www.tyan.com/products/html/ta26b2882.html
with 2 x OPTERON250 cpu's and 4 GIG of ECC ram.
There is 8 x scsi disks for storage
cupper gig-E for internal communication to spool/header servers etc.
acenic FiberOptic Gig-E 64bit PCI card for link to the internet.
Bandwidth use is sampled from the ethernet switch and with mrtg
visualised.
Take today for example:
http://newsgate.newsserver.nl/kernel/2.6.14-rc1-ethernet-bandwidth.png
>From yesterday till 10:30am i ran 2.6.13.1 in UP mode.
As you can see blue (==incoming traffic) is fairly constant.
This morning i compiled/installed 2.6.14-rc1-smp.
I let it ran till 12:15 but it's clear that it can't keep up
with the flow of data. I rebooted to 2.6.14-rc1 (UP) and that
keeps up with the data just fine.
So what is the difference between UP & SMP ?
shared memory , shared interrupts.
I don't know _why_ it's living up to _my_ expectation.
I hoped that the load would drop (it's between 4 to 5) op UP kernel
because certain processes would be split over the processors.
Anybody want to try and explain to me where i'm making an error ?
Config file & kern.log output can be found at :
http://newsgate.newsserver.nl/kernel/
A very confused
Danny
next reply other threads:[~2005-09-13 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 21:12 Danny ter Haar [this message]
2005-09-13 21:54 ` Andrew Walrond
2005-09-14 6:16 ` Danny ter Haar
2005-09-14 7:58 ` Andrew Walrond
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='dg7fbf$5df$1@news.cistron.nl' \
--to=dth@cistron.nl \
--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®