Difference between revisions of "Talk:Cgroups"

From ArchWiki
Jump to: navigation, search
(Created page with "Perhaps this page should include how to do the famous <strike>200 line kernel patch</strike> 4 line bash script? ie. http://www.webupd8.org/2010/11/alternative-to-200-lines-kerne...")
 
(Help me understand cgroups: new section)
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
Perhaps this page should include how to do the famous <strike>200 line kernel patch</strike> 4 line bash script?
 
Perhaps this page should include how to do the famous <strike>200 line kernel patch</strike> 4 line bash script?
 
ie. http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html --[[User:Unhammer|Unhammer]] 08:09, 11 January 2011 (EST)
 
ie. http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html --[[User:Unhammer|Unhammer]] 08:09, 11 January 2011 (EST)
 +
 +
The bash script in question appears to be out-of-date, does anyone have an updated version? [[User:RunningDroid|RunningDroid]] ([[User talk:RunningDroid|talk]]) 19:48, 9 June 2013 (UTC)
 +
 +
== Help me understand cgroups ==
 +
 +
The matlab example given to me is a reason NOT to use cgroups.  Why in the world would we want to limit a calculation intensive operation like this it 75 % of the CPU resources?  Just nice matlab down to -19 and let it do its thing,  I do this all the time with makepkg while I compile for hours.  I can use the system and I do not experience any lags while makepkg is calling gcc using all my cores.

Revision as of 13:46, 28 July 2013

Perhaps this page should include how to do the famous 200 line kernel patch 4 line bash script? ie. http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html --Unhammer 08:09, 11 January 2011 (EST)

The bash script in question appears to be out-of-date, does anyone have an updated version? RunningDroid (talk) 19:48, 9 June 2013 (UTC)

Help me understand cgroups

The matlab example given to me is a reason NOT to use cgroups. Why in the world would we want to limit a calculation intensive operation like this it 75 % of the CPU resources? Just nice matlab down to -19 and let it do its thing, I do this all the time with makepkg while I compile for hours. I can use the system and I do not experience any lags while makepkg is calling gcc using all my cores.