linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John <da_audiophile@yahoo.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"david.heidelberger@ixit.cz" <david.heidelberger@ixit.cz>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"x86@kernel.org" <x86@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] expand micro-optimizations in kernel to newer model CPUs
Date: Sun, 15 Dec 2013 04:42:50 -0800 (PST)	[thread overview]
Message-ID: <1387111370.81380.YahooMailNeo@web140001.mail.bf1.yahoo.com> (raw)
In-Reply-To: <CAFLxGvxakZS5FFQcZ_ogTd9aUENT3ECj2Lxs+FCbZAiGqgOJ7g@mail.gmail.com>





----- Original Message -----
> From: Richard Weinberger <>
>
> A *very* small speedup.
> 
> And I really doubt your numbers.
> Why are you using ANOVA? You're comparing *two* groups not more than two.
> I had a quick look at your raw numbers, they don't seem to be normally
> distributed at all.
> Did you remove some peaks?
> 


Hi Richard.  Thank you for your interest.  Yes, a small speedup as I mentioned but  I'll note that the current kernel code includes the MCORE2 option.  I tested this against some of the newer ones and they are all on par with each other.  For example, here are differences in median values:

CPUDifference in median value
core2        +87.5 ms
core7-avx+79.7 ms
core-avx-i+257.2 ms

I am using ANOVA to establish that the generic group differs from the optimized group.  I have always used ANOVA for this sort of comparison whether using two or more groups.  In fact, thumb through any medical or scientific journal, you'll see others in pier reviewed article doing the same.  

I did not remove any datapoints; I do not understand why you don't think the sets are normally distributed.  Did you see the normal quantile plots?  Additionally, the population variances are fairly equal (Levene and Barlett tests). 

  reply	other threads:[~2013-12-15 12:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 15:53 [PATCH] expand micro-optimizations in kernel to newer model CPUs John
2013-12-10  3:51 ` David Heidelberger
2013-12-13 12:37   ` Austin S Hemmelgarn
     [not found]     ` <1387051250.86178.YahooMailNeo@web140005.mail.bf1.yahoo.com>
     [not found]       ` <ce679ca5-bf83-4c2a-9234-859cc7a4206b@email.android.com>
     [not found]         ` <1387057337.97000.YahooMailNeo@web140004.mail.bf1.yahoo.com>
     [not found]           ` <52ACECC4.208@zytor.com>
2013-12-15 12:00             ` John
2013-12-15 12:27               ` Richard Weinberger
2013-12-15 12:42                 ` John [this message]
2013-12-15 13:23                   ` Borislav Petkov
2013-12-15 17:31                   ` Richard Weinberger
2013-12-16 14:28               ` Ingo Molnar
2013-12-17 12:59                 ` Austin S Hemmelgarn
2013-12-15 12:23     ` John

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=1387111370.81380.YahooMailNeo@web140001.mail.bf1.yahoo.com \
    --to=da_audiophile@yahoo.com \
    --cc=akpm@linux-foundation.org \
    --cc=david.heidelberger@ixit.cz \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=richard.weinberger@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).