public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gigabyte mobo latency
Date: Sat, 18 Oct 2014 18:00:14 +0200	[thread overview]
Message-ID: <54428E8E.5080407@googlemail.com> (raw)
In-Reply-To: <loom.20141018T172004-713@post.gmane.org>

Am 18.10.2014 um 17:49 schrieb James:
> Hello,
>
>
> OK, so I run a minimalist DE (LXDE) and htop to monitor
> system performance. The mobo has an fx8350 with 8 cores
> (currently set at 4GHz (unclocked). The system rarily
> uses over 8/32 gig of it's ram. So the resources are not
> even close to exhausted. cpus mostly idle.
>
> I do keep (2) browsers up, with tabs aplenty, but they are not being used
> very much. It's mostly a myriad of documents to read while I hack at code.
>
> Often the latency is minimal and the system response (as guaged)
> from the keyboard is fine (quick). Other times the active terminal
> session is a pig mostly in the web browser windows.
>
> So. Is there a make.conf setting or elsewhere to make the 
> terminal session response times, in the browsers (seamonkey, firefox)
> faster?  Something like a ram_disk just for the browsers?
>
> Note, after I finish up a project, many (browser) terminal sessions
> are deleted and things are fine again. I'm just asking for a way
> to ensure more ram/cpu resources are dedicated to the browsers
> to boost performance, on a dynamic basis (without manual intervention).
>
> Maybe a ram_disk_cache  (dynamic renice to-10 for the active window?) just
> for the active browser window (the browser window I'm typing in? (background
> code compilations are not concurrent with
> the typing latency in the browser windows).....
>
> ideas?
>
>
> James
>
>
>

idea: have a look at the websites you visit. Some load&run megabytes of
javascript which bogs down everything. Nothing you can do about that
except turning of js.


  reply	other threads:[~2014-10-18 16:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-18 15:49 [gentoo-user] gigabyte mobo latency James
2014-10-18 16:00 ` Volker Armin Hemmann [this message]
2014-10-18 16:26   ` [gentoo-user] " James
2014-10-18 19:27     ` Philip Webb
2014-10-18 20:24       ` Volker Armin Hemmann
2014-10-18 20:34         ` Neil Bothwick
2014-10-18 21:39         ` James
2014-10-19 11:25           ` Dale
2014-10-18 21:25 ` [gentoo-user] " thegeezer
2014-10-18 21:51   ` [gentoo-user] " James
2014-10-18 23:02     ` thegeezer
2014-10-19  3:15       ` James
2014-10-19 12:02         ` thegeezer
2014-10-19 16:41           ` James
2014-10-19 17:03             ` Dale
2014-10-19 20:03               ` James
2014-10-20  3:13                 ` Dale
2014-10-19 18:56             ` Rich Freeman
2014-10-19 20:40               ` James
2014-10-19 20:57                 ` Alan McKinnon
2014-10-19 21:35                 ` Rich Freeman
2014-10-19 21:45               ` Volker Armin Hemmann
2014-10-19 23:34                 ` Rich Freeman
2014-10-21 17:41                   ` Volker Armin Hemmann
2014-10-22  1:35 ` Nikos Chantziaras

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=54428E8E.5080407@googlemail.com \
    --to=volkerarmin@googlemail.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