From: Farkas Levente <lfarkas@bppiac.hu>
To: Andrea Arcangeli <andrea@qumranet.com>
Cc: Cam Macdonell <cam@cs.ualberta.ca>, kvm@vger.kernel.org
Subject: Re: Benchmarking on CentOS 5
Date: Thu, 29 May 2008 12:13:01 +0200 [thread overview]
Message-ID: <483E81AD.9050209@bppiac.hu> (raw)
In-Reply-To: <20080529092309.GH8086@duo.random>
Andrea Arcangeli wrote:
> On Wed, May 28, 2008 at 10:27:08PM +0200, Farkas Levente wrote:
>> ok. so what is qumranet recommendation?
>
> I'm not aware of a Qumranet reccomandation for this but I can give you
> my opinion.
>
>> the just released latest rhel 5.2 kernel is kernel-2.6.18-92.el5 is it good
>> enough for kvm host os? or its' better to change some other distro eg:
>> fedora 9?
>> until now we try to use the latest rhel/centos on all of our servers while
>> we use fedora (currently 8 but may be upgrade in a few weeks if 9 become
>> stable) on desktops. but now it seems probably then for a kvm host
>> rhel/centos is not enough:-(
>
> This is a almost the opposite question of the previous one from Cam
> ;), here you're asking about a production kernel, Cam was asking for a
> benchmarking setup.
>
> I think any distro enterprise kernel is better for production systems
> than a latest mainline, but that's just me. You'll find others
> preferring to run 2.6.25 in production a few days after it is
> released.
>
> The slowdown we're talking about here for the preempt notifiers isn't
> going to make a big difference in a production system, more important
> that you're sure your host kernel is rock solid and well tested
> IMHO. But if it was pure benchmarking what you were doing, then using
> latest mainline was better to get the best possible score, that is why
> such printk is there.
i want rock solid, but smp guest and both 32 and 64bit guest centos too.
5-10% performance lost is not important but 50-200% is important. so my
real question is that kernel-2.6.18-92.el5 has "enough" features for an
good working kvm if i recompile kvm and kvm-kmod? ehough here means no
more than 5-10% performance lost.
--
Levente "Si vis pacem para bellum!"
next prev parent reply other threads:[~2008-05-29 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 17:48 Benchmarking on CentOS 5 Cam Macdonell
2008-05-28 18:33 ` Andrea Arcangeli
2008-05-28 20:27 ` Farkas Levente
2008-05-29 9:23 ` Andrea Arcangeli
2008-05-29 10:13 ` Farkas Levente [this message]
[not found] ` <483F75CC.9010303@cisco.com>
[not found] ` <ac75d95a0805300601x4e8b7400sf03280c80813b09e@mail.gmail.com>
[not found] ` <48400371.3060208@cisco.com>
2008-05-30 17:30 ` Farkas Levente
2008-06-01 14:32 ` Andrea Arcangeli
2008-06-02 9:05 ` Amit Shah
2008-06-02 15:56 ` Dor Laor
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=483E81AD.9050209@bppiac.hu \
--to=lfarkas@bppiac.hu \
--cc=andrea@qumranet.com \
--cc=cam@cs.ualberta.ca \
--cc=kvm@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