public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Very bad latency on x86 desktop when a process is swapping: Am I expecting too much?
Date: Sun, 03 Oct 2010 16:55:17 -0700	[thread overview]
Message-ID: <i8b556$v3$1@dough.gmane.org> (raw)

Hi lkml,

This is most likely a corner case for the average linux desktop user, but
it's very annoying for me and I'd like to get a feel for what I 'should' be
expecting.

I track the mozilla-firefox-trunk sources from their hg repository every day,
and there is one place in the build where roughly 20-30 large libraries are
linked, all in one giant gcc command.

All those libraries won't fit in my puny 1GB of RAM, so the machine starts to
swap, naturally.

During the 2-3 minutes that all those libraries are being linked, the machine
is truly unusable for any normal lightweight desktop task like reading email.
The swap usage tops out at about 15% of available swap space.

I know the problem would go away if install more RAM, but that's not my real
question.

What should I realistically expect from a desktop workstation under these
fairly uncommon conditions?

Many thanks.


                 reply	other threads:[~2010-10-03 23:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='i8b556$v3$1@dough.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=linux-kernel@vger.kernel.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