[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH RFC V8 0/17] Paravirtualized ticket spinlocks
- To: Avi Kivity <avi@xxxxxxxxxx>
- From: Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>
- Date: Sun, 13 May 2012 23:29:28 +0530
- Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Greg Kroah-Hartman <gregkh@xxxxxxx>, KVM <kvm@xxxxxxxxxxxxxxx>, linux-doc@xxxxxxxxxxxxxxx, Srivatsa Vaddagiri <vatsa@xxxxxxxxxxxxxxxxxx>, Andi Kleen <andi@xxxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Gleb Natapov <gleb@xxxxxxxxxx>, X86 <x86@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Virtualization <virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx>, Marcelo Tosatti <mtosatti@xxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Attilio Rao <attilio.rao@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Stephan Diestelhorst <stephan.diestelhorst@xxxxxxx>
- Delivery-date: Tue, 15 May 2012 11:14:18 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 05/07/2012 05:36 PM, Avi Kivity wrote:
On 05/07/2012 01:58 PM, Raghavendra K T wrote:
On 05/07/2012 02:02 PM, Avi Kivity wrote:
On 05/07/2012 11:29 AM, Ingo Molnar wrote:
(Less is better. Below is time elapsed in sec for x86_64_defconfig
(3+3 runs)).
BASE BASE+patch %improvement
mean (sd) mean (sd)
case 1x: 66.0566 (74.0304) 61.3233 (68.8299) 7.16552
case 2x: 1253.2 (1795.74) 131.606 (137.358) 89.4984
case 3x: 3431.04 (5297.26) 134.964 (149.861) 96.0664
You're calculating the improvement incorrectly. In the last case, it's
not 96%, rather it's 2400% (25x). Similarly the second case is about
900% faster.
speedup calculation is clear.
I think confusion for me was more because of the types of benchmarks.
I always did
|(patch - base)| * 100 / base
So, for
(1) lesser is better sort of benchmarks,
improvement calculation would be like
|(patched - base)| * 100/ patched
e.g for kernbench,
suppose base = 150 sec
patched = 100 sec
improvement = 50 % ( = 33% degradation of base)
(2) for higher is better sort of benchmarks improvement calculation
would be like
|(patched - base)| * 100 / base
for e.g say for pgbench/ ebizzy...
base = 100 tps (transactions per sec)
patched = 150 tps
improvement = 50 % of pathched kernel ( OR 33 % degradation of base )
Is this is what generally done? just wanted to be on same page before
publishing benchmark results, other than kernbench.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
