From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: Linux-MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Nitin Gupta <ngupta@vflare.org>,
bob.liu@oracle.com, Mel Gorman <mgorman@suse.de>
Subject: Re: Testing results of zswap
Date: Mon, 15 Jul 2013 09:56:53 -0500 [thread overview]
Message-ID: <20130715145653.GA7275@medulla.variantweb.net> (raw)
In-Reply-To: <CAA_GA1fiEJYxqAZ1c0BneuftB5g8d+2_mYBj=4iE=1EcYaTx7w@mail.gmail.com>
On Mon, Jul 15, 2013 at 10:56:17AM +0800, Bob Liu wrote:
> As my test results showed in this thread.
> 1. Zswap only useful when total ram size is large else the performance
> was worse than disabled it!
I have not observed this. In my kernbench runs, I was using VMs with ~512MB
of RAM and saw significant improvement from zswap.
>
> 2. Zswap occupies some memory but that's unfair to file pages, more
> file pages maybe reclaimed during memory pressure.
This is true. It remains to be explored how the policies that balance anon
reclaim and page cache reclaim can be respected by zswap. Until then though,
the growth of the zswap pool does add memory pressure which causes more
reclaim in general, both anon and page cache.
> I think that's why the performance of the background io-duration was
> worse than disable zswap.
The I/O load during the parallelio-memcached test shouldn't be effected by
page cache reclaim since it is not re-reading anything. Again, I say that
that test is not a good and repeatable (across different systems and kernel
versions) to test zswap. parallelio-memcached is designed to test
suboptimal page reclaim decisions, not swap performance.
Have you tried running kernbench in a memory environment restricted enough
to cause swapping with zswap enabled? I think that would be a better test.
Seth
--
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>
next prev parent reply other threads:[~2013-07-15 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 2:03 Bob Liu
2013-07-15 2:56 ` Bob Liu
2013-07-15 14:56 ` Seth Jennings [this message]
2013-07-16 12:16 ` Bob Liu
2013-08-06 11:37 ` Wanpeng Li
2013-08-06 11:37 ` Wanpeng Li
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=20130715145653.GA7275@medulla.variantweb.net \
--to=sjenning@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lliubbo@gmail.com \
--cc=mgorman@suse.de \
--cc=ngupta@vflare.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