From: Jason Molenda <jason@molenda.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: overseers@sources.redhat.com
Subject: Re: splitting sourceware into pieces?
Date: Wed, 21 Feb 2001 13:16:00 -0000 [thread overview]
Message-ID: <20010221131545.A16859@shell17.ba.best.com> (raw)
In-Reply-To: <20010221130610.A11627@shell17.ba.best.com>
On Wed, Feb 21, 2001 at 01:06:10PM -0800, Jason Molenda wrote:
>
> I kind of doubt we're CPU starved very often, though.
>
I just logged into the system, and there actually is about 0% idle
on the CPU with just a few processes executing concurrently. I
still don't think this is where the real bottleneck is, but it does
mean that getting a second CPU or upgrading to a faster CPU could
help things a bit.
Jason
next prev parent reply other threads:[~2001-02-21 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 11:10 Phil Edwards
2001-02-21 12:51 ` Andrew Cagney
2001-02-21 14:28 ` Jason Molenda
2001-02-21 14:41 ` Phil Edwards
2001-02-21 15:27 ` Jason Molenda
2001-02-21 13:06 ` Jason Molenda
2001-02-21 13:16 ` Jason Molenda [this message]
2001-02-21 13:22 ` Phil Edwards
2001-02-26 8:43 ` Jeffrey A Law
2001-02-21 14:31 ` Jeffrey A Law
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=20010221131545.A16859@shell17.ba.best.com \
--to=jason@molenda.com \
--cc=overseers@sources.redhat.com \
--cc=pedwards@disaster.jaj.com \
/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).