public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] swap usage creeping up
Date: Mon, 15 Nov 2010 14:39:33 +0930	[thread overview]
Message-ID: <1289797773.3977.10.camel@localhost> (raw)
In-Reply-To: <AANLkTi=iLtq2kiq0qFUQfy=DdTpFBxUCRXSwcdz0vzZ8@mail.gmail.com>

On Tue, 2010-11-09 at 23:24 +0200, Fatih Tümen wrote: 
> On Fri, Nov 5, 2010 at 08:45, Iain Buchanan <iaindb@netspace.net.au> wrote:
> > OK so vm.swappiness seemed to help a bit but today I notice that swap
> > usage is up again.  It's firefox:
> >
> >  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> > 14072 iain      20   0 1369m 897m  15m S    3 29.5 113:14.91 firefox
> >
> > I think that's 1.3Gb + 900Mb... sounds like a memory leak to me.
> >
> > Anyone else run firefox for 113+ hours?  I'm using 3.6.9-r1.
> >
> 
> 1.3G is the grant total of Res and Swap.  You need to read man top
> before judging not-entirely-accurate values reported by top.

judging? I only said "I think"!

sure, top has it's quirks, but it's ok for comparing against itself.

> 900M is resident on your main memory. '113+ hours' is not a decent
> information to draw conclusion from. Running firefox for 113+ hours
> with a single tab on a text-only website is not same as running dozens
> of tabs with dozens of multimedia/embedded objects.

sure, but running it for 10 or 100 or 1000 hours should produce roughly
the same characteristics for the same browsing behaviour if all other
things are equal.  A few months ago this didn't cause any issues at all,
now I'm seeing high swap usage.  I usually never use my 3G of physical
RAM.

Again today I see it is using about 900Mb in total, which seems quite
large.  vm.swappiness is set to 0.  I've upgraded firefox to 3.6.12.

I had to reboot, but I'll check the usual statistics next time I see it.

-- 
Iain Buchanan <iaindb@netspace.net.au>





  reply	other threads:[~2010-11-15  5:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  5:49 [gentoo-user] swap usage creeping up Iain Buchanan
2010-10-26  6:16 ` Adam Carter
2010-10-26  6:57   ` Iain Buchanan
2010-10-26  6:30 ` Fatih Tümen
2010-10-26  7:02   ` Iain Buchanan
2010-10-26  7:18     ` Fatih Tümen
2010-10-27 22:47     ` Iain Buchanan
2010-10-27 23:44       ` Neil Bothwick
2010-10-27 23:59         ` Dale
2010-10-28  1:12           ` Adam Carter
2010-10-28  3:56             ` Dale
2010-10-28  4:34               ` Adam Carter
2010-10-28  6:32                 ` Dale
2010-11-05  6:45                   ` Iain Buchanan
2010-11-05 13:48                     ` [gentoo-user] " walt
2010-11-09 21:24                     ` [gentoo-user] " Fatih Tümen
2010-11-15  5:09                       ` Iain Buchanan [this message]
2010-11-15  8:41                         ` Fatih Tümen
2010-11-15 14:14                           ` Iain Buchanan
2010-11-15 15:26                             ` Fatih Tümen
2010-11-15 23:43                               ` Dale
2010-11-16  1:17                                 ` Iain Buchanan
2010-10-26  7:10 ` Dale
2010-10-28 16:13 ` [gentoo-user] " James
2010-10-28 23:26   ` Iain Buchanan

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=1289797773.3977.10.camel@localhost \
    --to=iaindb@netspace.net.au \
    --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