All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
	Konrad Wilk <konrad.wilk@oracle.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: High slab usage testing with zcache/zswap (Was: [PATCH 7/8] zswap: add to mm/)
Date: Tue, 22 Jan 2013 15:58:53 -0800 (PST)	[thread overview]
Message-ID: <6dc259d4-440e-4926-bf5f-e9deb9a19f09@default> (raw)
In-Reply-To: <20130103073339.GF3120@dastard>

> From: Dave Chinner [mailto:david@fromorbit.com]
> Sent: Thursday, January 03, 2013 12:34 AM
> Subject: Re: [PATCH 7/8] zswap: add to mm/
> 
> > > On 01/02/2013 09:26 AM, Dan Magenheimer wrote:
> > > > However if one compares the total percentage
> > > > of RAM used for zpages by zswap vs the total percentage of RAM
> > > > used by slab, I suspect that the zswap number will dominate,
> > > > perhaps because zswap is storing primarily data and slab is
> > > > storing primarily metadata?
> > >
> > > That's *obviously* 100% dependent on how you configure zswap.  But, that
> > > said, most of _my_ systems tend to sit with about 5% of memory in
> > > reclaimable slab
> >
> > The 5% "sitting" number for slab is somewhat interesting, but
> > IMHO irrelevant here. The really interesting value is what percent
> > is used by slab when the system is under high memory pressure; I'd
> > imagine that number would be much smaller.  True?
> 
> Not at all. The amount of slab memory used is wholly dependent on
> workload. I have plenty of workloads with severe memory pressure
> that I test with that sit at a steady state of >80% of ram in slab
> caches. These workloads are filesytem metadata intensive rather than
> data intensive, that's exactly the right cache balance for the
> system to have....

Hey Dave --

I'd like to do some zcache policy testing where the severe
memory pressure is a result of something like the above
where >80% of ram is in slab caches.  Any thoughts on how
to do this or easily simulate it on a very simple hardware
system (e.g. PC with one SATA disk)?  Or is a "big data"
configuration required?

Thanks for any advice!
Dan

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>,
	Konrad Wilk <konrad.wilk@oracle.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: High slab usage testing with zcache/zswap (Was: [PATCH 7/8] zswap: add to mm/)
Date: Tue, 22 Jan 2013 15:58:53 -0800 (PST)	[thread overview]
Message-ID: <6dc259d4-440e-4926-bf5f-e9deb9a19f09@default> (raw)
In-Reply-To: <20130103073339.GF3120@dastard>

> From: Dave Chinner [mailto:david@fromorbit.com]
> Sent: Thursday, January 03, 2013 12:34 AM
> Subject: Re: [PATCH 7/8] zswap: add to mm/
> 
> > > On 01/02/2013 09:26 AM, Dan Magenheimer wrote:
> > > > However if one compares the total percentage
> > > > of RAM used for zpages by zswap vs the total percentage of RAM
> > > > used by slab, I suspect that the zswap number will dominate,
> > > > perhaps because zswap is storing primarily data and slab is
> > > > storing primarily metadata?
> > >
> > > That's *obviously* 100% dependent on how you configure zswap.  But, that
> > > said, most of _my_ systems tend to sit with about 5% of memory in
> > > reclaimable slab
> >
> > The 5% "sitting" number for slab is somewhat interesting, but
> > IMHO irrelevant here. The really interesting value is what percent
> > is used by slab when the system is under high memory pressure; I'd
> > imagine that number would be much smaller.  True?
> 
> Not at all. The amount of slab memory used is wholly dependent on
> workload. I have plenty of workloads with severe memory pressure
> that I test with that sit at a steady state of >80% of ram in slab
> caches. These workloads are filesytem metadata intensive rather than
> data intensive, that's exactly the right cache balance for the
> system to have....

Hey Dave --

I'd like to do some zcache policy testing where the severe
memory pressure is a result of something like the above
where >80% of ram is in slab caches.  Any thoughts on how
to do this or easily simulate it on a very simple hardware
system (e.g. PC with one SATA disk)?  Or is a "big data"
configuration required?

Thanks for any advice!
Dan

  parent reply	other threads:[~2013-01-22 23:59 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<1355262966-15281-1-git-send-email-sjenning@linux.vnet.ibm.com>
     [not found] ` <<1355262966-15281-8-git-send-email-sjenning@linux.vnet.ibm.com>
2012-12-31 23:06   ` [PATCH 7/8] zswap: add to mm/ Dan Magenheimer
2012-12-31 23:06     ` Dan Magenheimer
2013-01-01 17:52     ` Seth Jennings
2013-01-01 17:52       ` Seth Jennings
2013-01-02 15:55       ` Dave Hansen
2013-01-02 15:55         ` Dave Hansen
2013-01-02 17:26         ` Dan Magenheimer
2013-01-02 17:26           ` Dan Magenheimer
2013-01-02 18:17           ` Dave Hansen
2013-01-02 18:17             ` Dave Hansen
2013-01-02 19:04             ` Dan Magenheimer
2013-01-02 19:04               ` Dan Magenheimer
2013-01-03  7:33               ` Dave Chinner
2013-01-03  7:33                 ` Dave Chinner
2013-01-03 22:37                 ` Dan Magenheimer
2013-01-03 22:37                   ` Dan Magenheimer
2013-01-04  2:30                   ` Dave Chinner
2013-01-04  2:30                     ` Dave Chinner
2013-01-04 15:55                     ` Seth Jennings
2013-01-04 15:55                       ` Seth Jennings
2013-01-04 18:45                     ` Dan Magenheimer
2013-01-04 18:45                       ` Dan Magenheimer
2013-01-22 23:58                 ` Dan Magenheimer [this message]
2013-01-22 23:58                   ` High slab usage testing with zcache/zswap (Was: [PATCH 7/8] zswap: add to mm/) Dan Magenheimer
2013-01-02 22:44         ` [PATCH 7/8] zswap: add to mm/ Seth Jennings
2013-01-02 22:44           ` Seth Jennings
2013-01-02 17:08       ` Dan Magenheimer
2013-01-02 17:08         ` Dan Magenheimer
2013-01-02 23:25         ` Seth Jennings
2013-01-02 23:25           ` Seth Jennings
2013-01-03 22:33           ` Dan Magenheimer
2013-01-03 22:33             ` Dan Magenheimer
2013-01-04 15:42             ` Seth Jennings
2013-01-04 15:42               ` Seth Jennings
2013-01-04 22:45               ` Dan Magenheimer
2013-01-04 22:45                 ` Dan Magenheimer
2013-01-07 14:47                 ` Seth Jennings
2013-01-07 14:47                   ` Seth Jennings
2012-12-11 21:55 [PATCH 0/8] zswap: compressed swap caching Seth Jennings
2012-12-11 21:55 ` Seth Jennings
2012-12-11 21:55 ` [PATCH 1/8] staging: zsmalloc: add gfp flags to zs_create_pool Seth Jennings
2012-12-11 21:55   ` Seth Jennings
2012-12-11 21:56 ` [PATCH 2/8] staging: zsmalloc: remove unsed pool name Seth Jennings
2012-12-11 21:56   ` Seth Jennings
2012-12-11 21:56 ` [PATCH 3/8] staging: zsmalloc: add page alloc/free callbacks Seth Jennings
2012-12-11 21:56   ` Seth Jennings
2012-12-11 21:56 ` [PATCH 4/8] staging: zsmalloc: make CLASS_DELTA relative to PAGE_SIZE Seth Jennings
2012-12-11 21:56   ` Seth Jennings
2012-12-11 21:56 ` [PATCH 5/8] debugfs: add get/set for atomic types Seth Jennings
2012-12-11 21:56   ` Seth Jennings
2012-12-11 21:56 ` [PATCH 6/8] zsmalloc: promote to lib/ Seth Jennings
2012-12-11 21:56   ` Seth Jennings
2012-12-11 21:56 ` [PATCH 7/8] zswap: add to mm/ Seth Jennings
2012-12-11 21:56   ` Seth Jennings
2013-01-03 16:07   ` Seth Jennings
2013-01-03 16:07     ` Seth Jennings
2012-12-11 21:56 ` [PATCH 8/8] zswap: add documentation Seth Jennings
2012-12-11 21:56   ` Seth Jennings
2012-12-11 22:01 ` [PATCH 0/8] zswap: compressed swap caching Greg Kroah-Hartman
2012-12-11 22:01   ` Greg Kroah-Hartman
2012-12-12 16:29   ` Seth Jennings
2012-12-12 16:29     ` Seth Jennings
2012-12-12 17:27     ` Dan Magenheimer
2012-12-12 17:27       ` Dan Magenheimer
2012-12-12 18:32       ` Seth Jennings
2012-12-12 18:32         ` Seth Jennings
2012-12-12 18:36 ` Seth Jennings
2012-12-12 22:49 ` Luigi Semenzato
2012-12-12 22:49   ` Luigi Semenzato
2012-12-12 23:46   ` Dan Magenheimer
2012-12-12 23:46     ` Dan Magenheimer
2012-12-14 15:59   ` Seth Jennings
2012-12-14 15:59     ` Seth Jennings
2013-01-03 16:01 ` Seth Jennings
2013-01-03 16:01   ` Seth Jennings

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=6dc259d4-440e-4926-bf5f-e9deb9a19f09@default \
    --to=dan.magenheimer@oracle.com \
    --cc=david@fromorbit.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sjenning@linux.vnet.ibm.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.