From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gigabyte mobo latency
Date: Sat, 18 Oct 2014 21:51:04 +0000 (UTC) [thread overview]
Message-ID: <loom.20141018T233956-266@post.gmane.org> (raw)
In-Reply-To: 5442DAC8.2030106@thegeezer.net
thegeezer <thegeezer <at> thegeezer.net> writes:
> > So. Is there a make.conf setting or elsewhere to make the
> > terminal session response times, in the browsers (seamonkey, firefox)
> > faster?
> > the typing latency in the browser windows).....
> > ideas?
> two things you might like to look into: 1. cgroups (including freezer)
> to help isolate your browsers and also 2. look at atop instead of htop
> as this includes disk io
2. The system rarely uses 8 G of the 32 G available, so disk IO is
not the problem. No heavy writes. It was the java scripts....
1. Ahhhhhhhhhhhhhhhhhhh! tell me more. I found these links quickly:
https://www.kernel.org/doc/Documentation/cgroups/freezer-subsystem.txt
http://wiki.gentoo.org/wiki/LXC#Freezer_Support
I'm not sure if you've read any of my clustering_frustration posts
over the last month or so, but cgroups is at the heart of clustering now.
It seems many of the systemd based cluster solutions are having all
sorts of OOM, OOM-killer etc etc issues. So any and all good information,
examples and docs related to cgroups is of keen interests to me. My efforts
to build up a mesos/spark cluster, center around openrc and therefore
direct management of resources via cgroups.
The freezer is exactly what I'm looking for. Maybe I also need to read up
on lxc? What are the best ways to dynamically manage via cgroups? A gui?
A static config file? a CLI tool?
curiously,
James
next prev parent reply other threads:[~2014-10-18 21:51 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
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 ` James [this message]
2014-10-18 23:02 ` [gentoo-user] " 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=loom.20141018T233956-266@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