From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Hungry firefox
Date: Wed, 1 Apr 2015 15:38:44 +0000 (UTC) [thread overview]
Message-ID: <loom.20150401T171831-243@post.gmane.org> (raw)
In-Reply-To: 9122646.azexhp1jHr@wstn
Peter Humphrey <peter <at> prh.myzen.co.uk> writes:
>
> Hello list,
>
> Has anyone else here noticed firefox consuming 15% or so of CPU time, even
> while it's not supposed to be doing anything? This is version 31.5.3, with
> just AdBlock Plus and YesScript added. I have remerged it and saw no
> difference.
>
> [ebuild R ] www-client/firefox-31.5.3::gentoo
Installed versions: 31.5.3(01:48:14 AM 03/28/2015)(bindist dbus gstreamer
jit minimal
Well yes and no. Not according to htop. Seamonkey is the resource hog;
or using the most resources (40-60 %). Firefox is 1-4%. I keep both
open with dozens of tabs. The sad thing is my (8)( core amd 8350
with 32 Gig of ram is barely using (1) core, unless I compile a
big multi-thread package. What I do have is almost a full second of
keyboard response latency. I can close both and the system is snappy
on response. I open either one (FF or SM) and the 3 dozen or so tabs
and it's back to keyboard lag; even though the resource utilization is
scant (1-1.5 cores/8 and 5300/32093MB).
Since the kernel dev folks have change so much over the last few years.
I figure I need to take a long hard look at what is enabled in the kernel,
and how resources are awakened or idle'd via some kernel-profiling. It's
most likely some advanced power conservation feature(s) that need tweaking,
is my best guess.
I have a system with plenty of extra, expensive ram and idle cores should;
it not be sluggish, uniless a big hog of a single threaded process
is not being properly managed.
Even when my browsers are not (actively) being use but open, I get
the horrible sluggishness now; and I'm running lxde.......not kde.
Sometimes I can hardly type it's so bad. I have always had lots of
tabs open for years and not experienced this sort of lag. Minimal resource
utilization, but horrible lag.
I've installed and ran' sys-power/powertop and it has some interesting
information; but theres still no conclusion as to what is causing
this inherent systematic latency. I do suspect FF and SM and Thunderbird
are part of the problem, but overal resource utilzation is well below 20%
(ram and cores) all the time, except when compiling.
hth,
James
next prev parent reply other threads:[~2015-04-01 15:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 14:03 [gentoo-user] Hungry firefox Peter Humphrey
2015-04-01 15:03 ` Daniel Frey
2015-04-01 15:30 ` [gentoo-user] " Grant Edwards
2015-04-01 15:34 ` [gentoo-user] " Philip Webb
2015-04-01 15:44 ` Peter Humphrey
2015-04-01 16:18 ` Philip Webb
2015-04-01 16:30 ` Neil Bothwick
2015-04-01 20:48 ` [gentoo-user] " Grant Edwards
2015-04-02 7:28 ` [gentoo-user] " Philip Webb
2015-04-02 8:43 ` Neil Bothwick
2015-04-02 22:07 ` [gentoo-user] " »Q«
2015-04-02 23:02 ` [gentoo-user] " Frank Steinmetzger
2015-04-02 23:10 ` Frank Steinmetzger
2015-04-03 9:16 ` Philip Webb
2015-04-03 7:25 ` Stroller
2015-04-01 15:38 ` James [this message]
2015-04-01 17:43 ` wabenbau
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=loom.20150401T171831-243@post.gmane.org \
--to=wireless@tampabay.rr.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