public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gigabyte mobo latency
Date: Sun, 19 Oct 2014 13:02:44 +0100	[thread overview]
Message-ID: <5443A864.2030508@thegeezer.net> (raw)
In-Reply-To: <loom.20141019T041305-882@post.gmane.org>

On 19/10/14 04:15, James wrote:
> thegeezer <thegeezer <at> thegeezer.net> writes:
>
>
>> there is a little more here
>> http://gentoo-en.vfose.ru/wiki/Improve_responsiveness_with_cgroups
>> which will allow you to script creating a cgroup with the processID of
>> an interactive shell, that you can start from to help save hunting down
>> all the threads spawned by chrome.
>> you can then do fun stuff with echo $$ >
>> /sys/fs/cgroup/cpu/high_priority/tasks
> Yea this is cool. But when it's a cluster, with thousands of processes
cgroups are hierarchical, so for example if you start a bash script
which is in cgroup "cpu/high_prio" which then starts your processes, all
called programs go into the same cgroup which makes it a bit simpler.
also openrc will start your services in the correct cgroup too
> this seem to be limited by the manual parsing and CLI actions that
> are necessary for large/busy environments. (We shall see).
>
>> hopefully this will give you a bit more control over all of that though
>
> Gmane mandates that the previous lines be culled. That said; you have given
> me much to think about, test and refine. 
>
> In /sys/fs/cgroup/cpu   I have:
>
> cgroup.clone_children  cgroup.procs  cpu.shares      release_agent
> cgroup.event_control cgroup.sane_behavior notify_on_release  tasks
>
> So I'll have to research creating and priotizing dirs like "high_priority"
>
>
> I certainly appreciate your lucid and direct explanations.
> Let me play with this a bit and I'll post back when I munge things
> up.....   Are there any "graphical tools" for adjusting and managing
> cgroups?  
i thought that htop did this but i was wrong.. it only shows which
cgroup processes are in. that would be a killer feature though.
> Surely when I apply this to the myriad of things running
> on my mesos+spark cluster I'm going to need a well thoughout tool
> for cgroup management, 
especially for non-local systems.  other distros have apps such as
"cgclassify" which provides some shortcut to managing cgroups --
creation / and moving process in and out
you can also have a nohup process that does ps -eLf to search for
process you want to classify and move them into the appropriate cgroup  
for default cgroups you can also use inotify
a quick search shows http://libcg.sourceforge.net/ which daemonises this
process.
all this is a bit hack'n'slash though i appreciate, so if anyone else
knows of suitable tools i'd also be interested to hear of them    
> particularly on memory resources organization
> and allocations as spark is an "in_memory" environment that seems 
> sensitive to OOM issues of all sorts.
>
> thx,
> James
>
>
>
>



  reply	other threads:[~2014-10-19 12:03 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   ` [gentoo-user] " James
2014-10-18 23:02     ` thegeezer
2014-10-19  3:15       ` James
2014-10-19 12:02         ` thegeezer [this message]
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=5443A864.2030508@thegeezer.net \
    --to=thegeezer@thegeezer.net \
    --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