So I spent a few minutes trying to figure out what they were trying to do with this -- is it just that they're putting the "interactive" processes in their own scheduling group and this (or all?) scheduling groups get scheduled prior to hoi polloi ?<div>
<br></div><div>How is that any different from making the login shell be RT (and a suitably high priority)?</div><div><br></div><div>More importantly, what does this do to the actual through-put of the system? Doesn't it cause all sorts of crazy starvation that just ends up making the overall system sluggish (because of all sorts of retries and timeouts that have to get handled)?</div>
<div><br></div><div>Jeff</div><div><br>
<br><div class="gmail_quote">On Mon, Dec 13, 2010 at 9:44 PM, Bill Baker <span dir="ltr"><<a href="mailto:bill_chris@earthlink.net" target="_blank">bill_chris@earthlink.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Getting back to the subject of Linux...<br>
<br>
Has anyone tried out the new 200 line kernel patch that supposedly<br>
improves responsiveness? I just added the alternative script to<br>
my /etc/rc.local file that's supposed to do the same thing detailed<br>
here:<br>
<a href="http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html" target="_blank">http://www.webupd8.org/2010/11/alternative-to-200-lines-kernel-patch.html</a><br>
<br>
So far I don't see much of an improvement, but I'll continue to use it<br>
to see if I do notice anything. I was just checking to see if anyone<br>
had done the actual patch and if there was any dramatic improvement.<br>
<br>
_______________________________________________<br>
colug-432 mailing list<br>
<a href="mailto:colug-432@colug.net" target="_blank">colug-432@colug.net</a><br>
<a href="http://lists.colug.net/mailman/listinfo/colug-432" target="_blank">http://lists.colug.net/mailman/listinfo/colug-432</a><br>
</blockquote></div><br></div>