From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@suse.cz>, lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>
Subject: Re: [LSF/MM TOPIC ATTEND] - THP benefits
Date: Mon, 02 Feb 2015 09:37:18 +0100 [thread overview]
Message-ID: <54CF373E.4090200@suse.cz> (raw)
In-Reply-To: <20150106161435.GF20860@dhcp22.suse.cz>
On 01/06/2015 05:14 PM, Michal Hocko wrote:
> - THP success rate has become one of the metric for reclaim/compaction
> changes which I feel is missing one important aspect and that is
> cost/benefit analysis. It might be better to have more THP pages in
> some loads but the whole advantage might easily go away when the
> initial cost is higher than all aggregated saves. When it comes to
> benchmarks and numbers we are usually missing the later.
So what I think would help in this discussion is some numbers on how much
hugepages (thus THP) actually help performance nowadays. Does anyone have such
results on recent hardware from e.g. SPEC CPU2006 or even production workloads?
--
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>
prev parent reply other threads:[~2015-02-02 8:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 16:14 [LSF/MM TOPIC ATTEND] Michal Hocko
2015-01-06 23:27 ` Greg Thelen
2015-01-07 14:28 ` Michal Hocko
2015-01-07 18:54 ` Greg Thelen
2015-01-07 19:00 ` Greg Thelen
2015-01-14 21:27 ` Andrea Arcangeli
2015-01-15 14:06 ` Michal Hocko
2015-01-15 20:58 ` Andrea Arcangeli
2015-01-07 8:58 ` Vladimir Davydov
2015-01-07 14:38 ` Michal Hocko
2015-01-08 8:33 ` Vladimir Davydov
2015-01-08 9:09 ` Michal Hocko
2015-02-02 8:37 ` Vlastimil Babka [this message]
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=54CF373E.4090200@suse.cz \
--to=vbabka@suse.cz \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
/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).