From: "Fred ." <eldmannen@gmail.com>
To: linux-smp@vger.kernel.org
Subject: Is CFS in Linux broken, or is Xorg broken?
Date: Tue, 25 Nov 2008 01:39:19 +0100 [thread overview]
Message-ID: <f188924b0811241639h4417b0b9h863fe4ec270b69d9@mail.gmail.com> (raw)
I am running Ubuntu 8.10 with kernel 2.6.27, Xorg 7.4, Firefox 3.0.4.
I have a Intel Core 2 Duo 2.13 GHz system (dual-core, 4gb ram)
I clicked on a SVG image, and Firefox froze for several minutes. (
http://en.wikipedia.org/wiki/Image:Unix_history-simple.svg )
GNOME System Monitor said that core #1 used 100% CPU, and that core #2
used 0-5%.
But my whole desktop was slow and sluggish and a pain, it was
crawling, it was very slow.
Something is wrong here. Why was my desktop was so slow and
unresponsive, when I had a whole core free under no load?
Either the scheduler in the Linux kernel must be doing something
wrong, or the Xorg must be doing something wrong.
Which is the culprit? Where do we put the blame?
Either way, this needs to get fixed. Desktop Linux cant be this way.
reply other threads:[~2008-11-25 0:39 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=f188924b0811241639h4417b0b9h863fe4ec270b69d9@mail.gmail.com \
--to=eldmannen@gmail.com \
--cc=linux-smp@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).