public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: cgroupd really do work!
Date: Sun, 05 Dec 2010 09:10:12 +0800	[thread overview]
Message-ID: <1291511412.14011.9.camel@rattus> (raw)
In-Reply-To: <ide672$8jr$1@dough.gmane.org>

On Sat, 2010-12-04 at 11:52 -0800, walt wrote:
> On 12/03/2010 04:41 PM, William Kenworthy wrote:
> > Re the discussion on cgroups on the 24/25 november - on my old AMD
> > barton 2500+ desktop - in the past a load of anything more than 5 made
> > it very painful to use.  Add in running windows in a qemu vm at the same
> > time (all in 1.5G ram) and its almost unusable as an interactive
> > desktop.
> >
> > Now, with Florians (thanks for the scripts) version of using it on
> > gentoo, even at a load in excess of 12, its almost as good as with no
> > load for desktop operations!
> >
> > To get the high load I am compiling a new kernel, running win2k in qemu,
> > emerging latest updates, browsing the web and reading email in
> > evolution, running updatedb and other cron jobs (just restarted after a
> > tuxonice hibernate so everything is triggering at once!).
> 
> I would expect some disk swapping activity when running all those apps in
> 1.5GB of RAM.  Are you seeing any?
> 
> 

yes, a lot as expected (multiple disks using LVM) so no attempt to
configure the disks for high performance.  The compiles were quite slow,
but thats fine because I could still use the desktop.  The only
interactive app that didnt work well was the win2k instance running in
qemu - it did work, though slowly, and when the other jobs were over and
it could get more cpu time it came back to around normal.  qemu is
somewhat borderline on this machine in any case - been on it for 6-7
years though :)

Some apps that were swapped out had a very short delay while the pages
were retrieved (mainly noticable on firefox), but the before/after
impression was the difference between a very short pause and what used
to happen - time to take the hand off the mouse and lean back in the
chair and wait for FF to catch up.

Keep in mind this is a relatively low memory, very old/slow 32 bit
system I am using.

and after running this for a couple of days, yes, I am still happy with
it and this gives the old beast a new lease on life :)

BillK

-- 
William Kenworthy <billk@iinet.net.au>
Home in Perth!




      reply	other threads:[~2010-12-05  2:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04  0:41 [gentoo-user] cgroupd really do work! William Kenworthy
2010-12-04  1:20 ` Mark Knecht
2010-12-04  2:16   ` William Kenworthy
2010-12-04 21:00     ` Mark Knecht
2010-12-05 14:55       ` Florian Philipp
2010-12-05 15:35         ` Mark Knecht
2010-12-05 16:02         ` Florian Philipp
2010-12-05 23:54           ` Bill Longman
2010-12-06  4:51             ` Florian Philipp
2010-12-06 20:04           ` [gentoo-user] " Doug Hunley
2010-12-06 20:44             ` Doug Hunley
2010-12-06 22:00             ` Florian Philipp
2010-12-07  5:51         ` [gentoo-user] " Scott Prager
2010-12-07  8:43           ` Neil Bothwick
2010-12-04 19:52 ` [gentoo-user] " walt
2010-12-05  1:10   ` William Kenworthy [this message]

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=1291511412.14011.9.camel@rattus \
    --to=billk@iinet.net.au \
    --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