linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: [mm] e04ddfd12aa: +9.4% ebizzy.throughput
Date: Fri, 4 Apr 2014 21:59:08 +0800	[thread overview]
Message-ID: <20140404135908.GB22386@localhost> (raw)

Hi Davidlohr,

FYI, there are noticeable ebizzy throughput increases on commit
e04ddfd12aa03471eff7daf3bc2435c7cea8e21f ("mm: per-thread vma caching")

test case: lkp-st02/micro/ebizzy/200%-100-10

700141f349f2b05  e04ddfd12aa03471eff7daf3b  
---------------  -------------------------  
     23726 ~ 0%      +9.4%      25955 ~ 0%  TOTAL ebizzy.throughput
      1525 ~ 0%      +9.3%       1667 ~ 0%  TOTAL ebizzy.throughput.per_thread.max
      1428 ~ 0%      +9.1%       1558 ~ 0%  TOTAL ebizzy.throughput.per_thread.min
     14.42 ~ 0%      +8.1%      15.59 ~ 0%  TOTAL ebizzy.time.user
     65.29 ~ 0%      -1.8%      64.12 ~ 0%  TOTAL ebizzy.time.sys
      4290 ~17%     -28.4%       3073 ~22%  TOTAL slabinfo.buffer_head.active_objs
      4313 ~17%     -28.8%       3073 ~22%  TOTAL slabinfo.buffer_head.num_objs
    165372 ~ 0%      +9.2%     180527 ~ 0%  TOTAL vmstat.system.in
      1443 ~ 0%      +8.1%       1560 ~ 0%  TOTAL time.user_time
      6529 ~ 0%      -1.8%       6413 ~ 0%  TOTAL time.system_time

Legend:
	~XX%    - stddev percent
	[+-]XX% - change percent


                                  ebizzy.throughput

   26500 ++O-----------O---O------------------------------------------------+
         O   O O O O     O   O O O     O O                                  |
   26000 ++          O             O O      O     O                         |
         |                                 O  O O                           |
         |                                                                  |
   25500 ++                                                                 |
         |                                                                  |
   25000 ++                                                                 |
         |                                                                  |
   24500 ++                                                                 |
         |                                                                  |
         *.*.*.   .*. .*.*.*.   .*.*.       *.*.*.*.                        |
   24000 ++    *.*   *       *.*     *.*.*.*        *.*.*.*.*.*.            |
         |                                                      *.*.*.*.*.*.*
   23500 ++-----------------------------------------------------------------+


	[*] bisect-good sample
	[O] bisect-bad  sample

Thanks,
Fengguang

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2014-04-05  0:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 13:59 Fengguang Wu [this message]
2014-04-05  1:06 ` Davidlohr Bueso

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=20140404135908.GB22386@localhost \
    --to=fengguang.wu@intel.com \
    --cc=davidlohr@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@01.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