From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] tmp on tmpfs
Date: Fri, 26 May 2017 10:36:40 +1200 [thread overview]
Message-ID: <20170526103640.4bc8b4e5@katipo2.lan> (raw)
In-Reply-To: <20170524154545.3a09280850fe590357325959@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On Wed, 24 May 2017 15:45:45 +0300
Andrew Savchenko <bircoph@gentoo.org> wrote:
> - smaller CPU overhead: not every i/o is being compressed, e.g. if
> there is sill enough RAM available it is used without compression
> overhead as usual, but if memory is not enough, swapped out pages
> are being compressed instead of swapping out to disk;
I found the opposite problem somehow. CPU started becomming frequently pegged
in zswap for no obvious reason, while the underlying IO that zswap was doing
was only measurable in kb/s , far, far, far below the noise thresholds and
by no means a strain on even my crappy spinning rust based swap.
And to add to that, zswap introduced general protection faults and kernel panics.
So nah, I'm glad I turned that off, it was a huge mistake.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-25 22:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 5:16 [gentoo-user] tmp on tmpfs Ian Zimmerman
2017-05-24 5:34 ` gentoo-user
2017-05-24 6:00 ` [gentoo-user] " Kai Krakow
2017-05-24 17:05 ` Kai Krakow
2017-05-25 18:46 ` [gentoo-user] Puzzled by zswap [Was: tmp on tmpfs] Ian Zimmerman
2017-05-25 19:16 ` [gentoo-user] " Martin Vaeth
2017-05-26 6:00 ` Kai Krakow
2017-05-24 18:34 ` [gentoo-user] Re: tmp on tmpfs Ian Zimmerman
2017-05-24 19:30 ` Rich Freeman
2017-05-24 21:16 ` Andrew Savchenko
2017-05-24 22:40 ` Rich Freeman
2017-05-25 6:34 ` J. Roeleveld
2017-05-25 11:04 ` Kai Krakow
2017-05-25 12:23 ` Rich Freeman
2017-05-25 14:16 ` J. Roeleveld
2017-05-25 16:06 ` Rich Freeman
2017-05-25 16:28 ` J. Roeleveld
2017-05-25 16:41 ` Rich Freeman
2017-05-25 3:38 ` Kai Krakow
2017-05-25 7:19 ` J. Roeleveld
2017-05-25 3:36 ` Kai Krakow
2017-05-24 17:00 ` [gentoo-user] " R0b0t1
2017-05-24 6:03 ` Andrew Tselischev
2017-05-24 9:34 ` Rich Freeman
2017-05-24 9:43 ` gentoo-user
2017-05-24 9:54 ` Rich Freeman
2017-05-24 12:45 ` Andrew Savchenko
2017-05-25 4:45 ` [gentoo-user] " Martin Vaeth
2017-05-25 7:24 ` Mick
2017-05-25 15:46 ` Martin Vaeth
2017-05-25 22:36 ` Kent Fredric [this message]
2017-05-28 10:07 ` [gentoo-user] " Mick
2017-05-31 0:36 ` Kent Fredric
2017-05-31 7:33 ` Mick
2017-05-24 18:46 ` [gentoo-user] " Nikos Chantziaras
-- strict thread matches above, loose matches on Subject: below --
2017-05-29 11:09 [gentoo-user] Kernel did not finding root partition Raphael MD
2017-05-29 11:19 ` Rasmus Thomsen
2017-05-29 17:48 ` [gentoo-user] " Kai Krakow
2017-05-29 18:07 ` Raphael MD
2017-05-29 18:16 ` Neil Bothwick
2017-05-29 19:42 ` Kai Krakow
2017-05-30 8:26 ` Peter Humphrey
2017-05-30 17:08 ` Raphael MD
2017-05-30 18:05 ` Mick
2017-05-30 19:28 ` Kai Krakow
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=20170526103640.4bc8b4e5@katipo2.lan \
--to=kentnl@gentoo.org \
--cc=gentoo-user@lists.gentoo.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