public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernels & swap usage
Date: Fri, 10 Aug 2012 11:59:39 -0400	[thread overview]
Message-ID: <CA+czFiAxFZ33y3bpmPi956PyENkRiwzpTYxbK=C5vPNWKsXxLg@mail.gmail.com> (raw)
In-Reply-To: <50252861.1040407@binarywings.net>

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

On Fri, Aug 10, 2012 at 11:27 AM, Florian Philipp <lists@binarywings.net>wrote:

> Am 10.08.2012 08:56, schrieb Jesús J. Guerrero Botella:
> > It could be anything. Maybe some orphaned process was running in the
> > background and leaking ram, or something. It's futile to speculate now
> > about that.
> >
> > Also, the -recently added- "pgo" USE flag could have something to do
> > with that. Not sure, since I didn't bother to investigate it's true
> > purpose on firefox.
> >
>
> It does two compilations with a headless firefox benchmark in between.
> Except of doubling the compilation time, there is little difference in
> the compilation itself.
>

It enables profile-based optimizations. The resulting binary is much
faster, in my subjective experience.


>
> > I really don't think that the kernel has changed in a significant way
> > in this regard since the latests 2.6.x releases. But I certainly
> > didn't read *all* the kernel changelogs.
> >
>
> The latest thing of any significance I can think of is the removal of
> lumpy reclaim in 3.4 which has something to do with reducing memory
> fragmentation in systems under memory stress. LWN has a subscriber-only
> article about the change causing performance regressions. From my
> understanding of the code, I doubt it could cause an improvement in this
> particular situation.
>

I honestly think anyone having difficulties with swap should check out the
vm.swappiness sysctl before looking anywhere else. Setting it to 0 is much
like removing swap...except you still have the swap space if you actually
need it. On my work laptop, it looks like it defaults to a value of 60.

-- 
:wq

[-- Attachment #2: Type: text/html, Size: 2274 bytes --]

  reply	other threads:[~2012-08-10 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  5:02 [gentoo-user] kernels & swap usage Philip Webb
2012-08-08  6:15 ` Florian Philipp
2012-08-08  9:33   ` Philip Webb
2012-08-08 13:34     ` Florian Philipp
2012-08-08 17:24 ` Volker Armin Hemmann
2012-08-09 16:05   ` Jesús J. Guerrero Botella
2012-08-09 16:23     ` Philip Webb
2012-08-10  6:56       ` Jesús J. Guerrero Botella
2012-08-10 15:27         ` Florian Philipp
2012-08-10 15:59           ` Michael Mol [this message]
2012-08-10 17:24             ` Philip Webb

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='CA+czFiAxFZ33y3bpmPi956PyENkRiwzpTYxbK=C5vPNWKsXxLg@mail.gmail.com' \
    --to=mikemol@gmail.com \
    --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