Content-Type: multipart/mixed; boundary="===============4584808058435401361==" MIME-Version: 1.0 From: Fengguang Wu To: lkp@lists.01.org Subject: Re: [sched] 143e1e28cb4: +17.9% aim7.jobs-per-min, -9.7% hackbench.throughput Date: Tue, 12 Aug 2014 22:30:25 +0800 Message-ID: <20140812143025.GA12963@localhost> In-Reply-To: <20140811133352.GC9918@twins.programming.kicks-ass.net> List-Id: --===============4584808058435401361== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Mon, Aug 11, 2014 at 03:33:52PM +0200, Peter Zijlstra wrote: > On Sun, Aug 10, 2014 at 06:54:13PM +0800, Fengguang Wu wrote: > > This view may be easier to read, by grouping the metrics by test case. > > = > > test case: brickland1/aim7/6000-page_test > = > OK, I have a similar system to the brickland thing (slightly different > configuration, but should be close enough). > = > Now; do you have a description of each test-case someplace? You can find our aim7 test script here: git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tes= ts cd lkp-tests vi tests/aim7 More test scripts are available there: vi tests/hackbench vi tests/netperf ... > In particular, it might be good to have a small annotation to show > which direction is better. The directions are listed in these files as positive/negative numbers: vi metric/index-* For examples: % head -3 metric/index-* =3D=3D> metric/index-latency.yaml <=3D=3D dbench.max_latency: -0.1 fileio.request_latency_95%_ms: -0.2 oltp.request_latency_95%_ms: -0.2 =3D=3D> metric/index-perf.yaml <=3D=3D aim7.jobs-per-min: 1 dbench.throughput-MB/sec: 1 ebizzy.throughput: 1 =3D=3D> metric/index-power.yaml <=3D=3D turbostat.Pkg_W: -1 turbostat.RAM_W: -1 turbostat.%c0: -0.1 =3D=3D> metric/index-size.yaml <=3D=3D kernel-size.text: -1 kernel-size.data: -1 kernel-size.bss: -1 They are not the comprehensive list, but reasonably complete to list the most important ones. > > 128529 =C2=B1 1% +17.9% 151594 =C2=B1 0% TOTAL aim7.jobs-p= er-min > = > jobs per minute, + is better, so no worries there. > = > > 582269 =C2=B114% -55.6% 258617 =C2=B116% TOTAL softirqs.SC= HED > > 993654 =C2=B1 2% -19.9% 795962 =C2=B1 3% TOTAL softirqs.RCU > > 15865125 =C2=B1 1% -15.0% 13485882 =C2=B1 1% TOTAL softirqs.TI= MER > = > > 59366697 =C2=B1 3% -46.1% 32017187 =C2=B1 7% TOTAL cpuidle.C1-= IVT.time > > 54543 =C2=B111% -37.2% 34252 =C2=B116% TOTAL cpuidle.C1-= IVT.usage > > 19542 =C2=B1 9% -38.3% 12057 =C2=B1 4% TOTAL cpuidle.C1E= -IVT.usage > > 49527464 =C2=B1 6% -32.4% 33488833 =C2=B1 4% TOTAL cpuidle.C1E= -IVT.time > > 76064 =C2=B1 3% -32.2% 51572 =C2=B1 6% TOTAL cpuidle.C6-= IVT.usage > = > Less idle time; might be good, if the work is cpubound, might be bad if > not; hard to say. > = > > 2.82 =C2=B1 3% +21.9% 3.43 =C2=B1 4% TOTAL turbostat.%= pc2 > > 4.40 =C2=B1 2% +22.0% 5.37 =C2=B1 4% TOTAL turbostat.%= c6 > > 15.75 =C2=B1 1% -3.4% 15.21 =C2=B1 0% TOTAL turbostat.R= AM_W > = > > 3150464 =C2=B1 2% -24.2% 2387551 =C2=B1 3% TOTAL time.volunt= ary_context_switches > = > Typically less ctxsw is better.. > = > > 281 =C2=B1 1% -15.1% 238 =C2=B1 0% TOTAL time.elapse= d_time > > 29294 =C2=B1 1% -14.3% 25093 =C2=B1 0% TOTAL time.system= _time > = > Less time spend (on presumably the same work) is better > = > > 4529818 =C2=B1 1% -8.8% 4129398 =C2=B1 1% TOTAL time.involu= ntary_context_switches > = > Less preemptions, also generally better > = > > 10655 =C2=B1 0% +1.4% 10802 =C2=B1 0% TOTAL time.percen= t_of_cpu_this_job_got > = > Seem an improvement; not sure. > = > Many more stats.. but from the above it looks like its an overall 'win'; > or am I reading the thing wrong? I'd agree with your interpretations, too. In case you want to make sure the exact meaning of the above values: they are generated by scripts in stats/* and stats/hackbench would be a good example to read. Thanks, Fengguang --===============4584808058435401361==--