From: Daniel Wagner <wagi@monom.org>
To: Bernhard Schiffner <bernhard@schiffner-limbach.de>,
linux-rt-users@vger.kernel.org
Subject: Re: Some benchmark results
Date: Thu, 28 Aug 2014 08:11:47 +0200 [thread overview]
Message-ID: <53FEC823.5030709@monom.org> (raw)
In-Reply-To: <1657147.MGSNxR1uXh@bs8>
Hi Bernhard,
On 08/25/2014 04:14 PM, Bernhard Schiffner wrote:
> Am Montag, 25. August 2014, 11:02:32 schrieb Daniel Wagner:
>> Hi,
>>
>> I wanted to know how good or bad mainline vs RT is, therefore I let
>> MMTests torture my laptop for a while. I selected a few of the supported
>> benchmarks by MMTests in order to keep to a reasonable time frame.
>>
>> The aim was to see the impact of normal (no RT) workloads with different
>> preempt configurations on mainline and RT patched kernel. I tried to not
>> to change other configuration flags except the preempt one. There are
>> some small difference due to dependencies but the rest looks ok to me.
>>
>> http://www.monom.org/rt/mmtests/
>>
>> Suggestion, improvements, comments?
>>
>> cheers,
>> daniel
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Hi Daniel,
>
> I had a first look at the above mentioned page.
>
> The thing I'am complety missing in the huge amount of numbers is: What is your
> demand, your primary topic to solve in or with RT?
Thanks looking at the numbers and the feedback from you. I really
appreciate that.
To your question: My goal is to help out to get this patch set merged
into mainline. I know an ambitious goal and I might be too incompetent
(I may suffering from the Dunning–Kruger effect. but hey, I am not the
one who recognize this).
So I figured the best thing is to start playing with different loads and
see how they compare to mainline and trying to understand why they are
different.
> And as I interprete the numbers: a RT kernel is a little bit more CPU-hungry
> then normal and this is nothing new.
Sure, I am well aware that RT is 'a little bit more CPU-hungry', but I
wondered how much is a little and what are the effects of it?
I am doing those tests for myself to get a better understanding. I just
shared the results in case someone else finds them interesting. I should
have stated that more clearly to avoid burning time from you. Sorry
about that.
cheers,
daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-08-28 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 9:02 Some benchmark results Daniel Wagner
2014-08-25 14:14 ` Bernhard Schiffner
2014-08-28 6:11 ` Daniel Wagner [this message]
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=53FEC823.5030709@monom.org \
--to=wagi@monom.org \
--cc=bernhard@schiffner-limbach.de \
--cc=linux-rt-users@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.