All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de, akpm@osdl.org,
	jeremy@goop.org, xen-devel@lists.xensource.com,
	tmem-devel@oss.oracle.com, kurt.hackel@oracle.com,
	Russell <rusty@rustcorp.com.au>, Rik van Riel <riel@redhat.com>,
	dave.mccracken@oracle.com, linux-mm@kvack.org,
	Rusty@rcsinet15.oracle.com, sunil.mushran@oracle.com,
	Avi Kivity <avi@redhat.com>, Schwidefsky <schwidefsky@de.ibm.com>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	alan@lxorguk.ukuu.org.uk, chris.mason@oracle.com
Subject: Re: Tmem [PATCH 0/5] (Take 3): Transcendent memory
Date: Fri, 18 Dec 2009 09:06:31 +0100	[thread overview]
Message-ID: <20091218080631.GA1374@ucw.cz> (raw)
In-Reply-To: <23e2d3ad-2611-4422-9349-50e4d3d8377f@default>

Hi!

> Performance is difficult to quantify because some benchmarks respond
> very favorably to increases in memory and tmem may do quite well on
> those, depending on how much tmem is available which may vary widely
> and dynamically, depending on conditions completely outside of the
> system being measured.  Ideas on how best to provide useful metrics
> would be appreciated.

So... take 1GB system, run your favourite benchmark. Then reserve
512MB for tmem, rerun your benchmark, then run the system with
512MB/512MB swap, rerun the benchmark?

Tune the sizes so that first to last run differ by 100% or so, and see
how much first and second differs? If it is in 1% range, you are
probably doing good...?
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de, akpm@osdl.org,
	jeremy@goop.org, xen-devel@lists.xensource.com,
	tmem-devel@oss.oracle.com, kurt.hackel@oracle.com,
	Russell <rusty@rustcorp.com.au>, Rik van Riel <riel@redhat.com>,
	dave.mccracken@oracle.com, linux-mm@kvack.org,
	Rusty@rcsinet15.oracle.com, sunil.mushran@oracle.com,
	Avi Kivity <avi@redhat.com>, Schwidefsky <schwidefsky@de.ibm.com>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	alan@lxorguk.ukuu.org.uk, chris.mason@oracle.com
Subject: Re: Tmem [PATCH 0/5] (Take 3): Transcendent memory
Date: Fri, 18 Dec 2009 09:06:31 +0100	[thread overview]
Message-ID: <20091218080631.GA1374@ucw.cz> (raw)
In-Reply-To: <23e2d3ad-2611-4422-9349-50e4d3d8377f@default>

Hi!

> Performance is difficult to quantify because some benchmarks respond
> very favorably to increases in memory and tmem may do quite well on
> those, depending on how much tmem is available which may vary widely
> and dynamically, depending on conditions completely outside of the
> system being measured.  Ideas on how best to provide useful metrics
> would be appreciated.

So... take 1GB system, run your favourite benchmark. Then reserve
512MB for tmem, rerun your benchmark, then run the system with
512MB/512MB swap, rerun the benchmark?

Tune the sizes so that first to last run differ by 100% or so, and see
how much first and second differs? If it is in 1% range, you are
probably doing good...?
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

--
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:[~2009-12-18  8:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  0:36 Tmem [PATCH 0/5] (Take 3): Transcendent memory Dan Magenheimer
2009-12-18  0:36 ` Dan Magenheimer
2009-12-18  8:06 ` Pavel Machek [this message]
2009-12-18  8:06   ` Pavel Machek
2009-12-21 10:54 ` Nitin Gupta
  -- strict thread matches above, loose matches on Subject: below --
2009-12-21 13:46 Nitin Gupta
2009-12-21 13:46 ` Nitin Gupta
2009-12-21 23:46 ` Dan Magenheimer
2009-12-21 23:46   ` Dan Magenheimer
2009-12-23  6:28   ` Nitin Gupta
2009-12-23  6:28     ` Nitin Gupta
2009-12-23 17:15     ` Dan Magenheimer
2009-12-23 17:15       ` Dan Magenheimer
2009-12-24  3:27       ` Nitin Gupta
2009-12-24  3:27         ` Nitin Gupta
2009-12-24 20:51         ` Dan Magenheimer
2009-12-24 20:51           ` Dan Magenheimer
2009-12-25 19:18       ` Pavel Machek
2009-12-25 19:18         ` Pavel Machek
2009-12-28 15:57         ` Dan Magenheimer
2009-12-28 15:57           ` Dan Magenheimer
2009-12-28 20:51           ` Pavel Machek
2009-12-28 20:51             ` Pavel Machek
2009-12-28 21:41             ` Dan Magenheimer
2009-12-28 21:41               ` Dan Magenheimer
2009-12-29  2:07           ` Nitin Gupta
2009-12-29  2:07             ` Nitin Gupta

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=20091218080631.GA1374@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Rusty@rcsinet15.oracle.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=avi@redhat.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=chris.mason@oracle.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=dave.mccracken@oracle.com \
    --cc=jeremy@goop.org \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mtosatti@redhat.com \
    --cc=npiggin@suse.de \
    --cc=riel@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=schwidefsky@de.ibm.com \
    --cc=sunil.mushran@oracle.com \
    --cc=tmem-devel@oss.oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.