From: Luigi Semenzato <semenzato@google.com>
To: linux-mm@kvack.org, Minchan Kim <minchan@kernel.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Sonny Rao <sonnyrao@google.com>, Bryan Freed <bfreed@google.com>,
Hugh Dickins <hughd@google.com>
Subject: zram, OOM, and speed of allocation
Date: Wed, 28 Nov 2012 16:31:22 -0800 [thread overview]
Message-ID: <CAA25o9S5zpH_No+xgYuFSAKSRkQ=19Vf_aLgO1UWiajQxtjrpg@mail.gmail.com> (raw)
I am beginning to understand why zram appears to work fine on our x86
systems but not on our ARM systems. The bottom line is that swapping
doesn't work as I would expect when allocation is "too fast".
In one of my tests, opening 50 tabs simultaneously in a Chrome browser
on devices with 2 GB of RAM and a zram-disk of 3 GB (uncompressed), I
was observing that on the x86 device all of the zram swap space was
used before OOM kills happened, but on the ARM device I would see OOM
kills when only about 1 GB (out of 3) was swapped out.
I wrote a simple program to understand this behavior. The program
(called "hog") allocates memory and fills it with a mix of
incompressible data (from /dev/urandom) and highly compressible data
(1's, just to avoid zero pages) in a given ratio. The memory is never
touched again.
It turns out that if I don't limit the allocation speed, I see
premature OOM kills also on the x86 device. If I limit the allocation
to 10 MB/s, the premature OOM kills stop happening on the x86 device,
but still happen on the ARM device. If I further limit the allocation
speed to 5 Mb/s, the premature OOM kills disappear also from the ARM
device.
I have noticed a few time constants in the MM whose value is not well
explained, and I am wondering if the code is tuned for some ideal
system that doesn't behave like ours (considering, for instance, that
zram is much faster than swapping to a disk device, but it also uses
more CPU). If this is plausible, I am wondering if anybody has
suggestions for changes that I could try out to obtain a better
behavior with a higher allocation speed.
Thanks!
Luigi
--
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 reply other threads:[~2012-11-29 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 0:31 Luigi Semenzato [this message]
2012-11-29 18:46 ` zram, OOM, and speed of allocation Luigi Semenzato
2012-11-29 19:31 ` Luigi Semenzato
2012-11-29 20:55 ` Sonny Rao
2012-11-29 21:33 ` Luigi Semenzato
2012-11-29 22:57 ` Sonny Rao
2013-02-17 2:49 ` Jaegeuk Hanse
2012-12-03 6:42 ` Minchan Kim
2012-12-03 7:38 ` Minchan Kim
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='CAA25o9S5zpH_No+xgYuFSAKSRkQ=19Vf_aLgO1UWiajQxtjrpg@mail.gmail.com' \
--to=semenzato@google.com \
--cc=bfreed@google.com \
--cc=dan.magenheimer@oracle.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sonnyrao@google.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 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).