On Wed, Dec 18, 2013 at 03:28:14PM +0800, Fengguang Wu wrote: > Hi Mel, > > I'd like to share some test numbers with your patches applied on top of v3.13-rc3. > > Basically there are > > 1) no big performance changes > > 76628486 -0.7% 76107841 TOTAL vm-scalability.throughput > 407038 +1.2% 412032 TOTAL hackbench.throughput > 50307 -1.5% 49549 TOTAL ebizzy.throughput > I'm assuming this was an ivybridge processor. How many threads were ebizzy tested with? The memory ranges used by the vm scalability benchmarks are probably too large to be affected by the series but I'm guessing. I doubt hackbench is doing any flushes and the 1.2% is noise. > 2) huge proc-vmstat.nr_tlb_* increases > > 99986527 +3e+14% 2.988e+20 TOTAL proc-vmstat.nr_tlb_local_flush_one > 3.812e+08 +2.2e+13% 8.393e+19 TOTAL proc-vmstat.nr_tlb_remote_flush_received > 3.301e+08 +2.2e+13% 7.241e+19 TOTAL proc-vmstat.nr_tlb_remote_flush > 5990864 +1.2e+15% 7.032e+19 TOTAL proc-vmstat.nr_tlb_local_flush_all > The accounting changes can be mostly explained by "x86: mm: Clean up inconsistencies when flushing TLB ranges". flush_all was simply not being counted before so I would claim that the old figure was simply wrong and did not reflect reality. Alterations on when range versus global flushes would affect the other counters but arguably it's now behaving as originally intended by the tlb flush shift. > Here are the detailed numbers. eabb1f89905a0c809d13 is the HEAD commit > with 4 patches applied. The "~ N%" notations are the stddev percent. > The "[+-] N%" notations are the increase/decrease percent. The > brickland2, lkp-snb01, lkp-ib03 etc. are testbox names. > Are positive numbers always better? If so, most of these figures look good to me and support the series being merged. Please speak up if that is in error. I do see a few major regressions like this > 324497 ~ 0% -100.0% 0 ~ 0% brickland2/micro/vm-scalability/16G-truncate but I have no idea what the test is doing and whether something happened that the test broke that time or if it's something to be really concerned about. Thanks -- Mel Gorman SUSE Labs -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>