From: "Jack Johnson" <knapjack@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] why I'm messing with python: mercurial
Date: Sun, 24 Dec 2006 17:00:08 -0800 [thread overview]
Message-ID: <6e35c0620612241700h50fd3b0aw1d326216c9ae2c3b@mail.gmail.com> (raw)
In-Reply-To: <69898e3538bf13a71cf2403dd5e3d48e@hamnavoe.com>
On 12/24/06, Richard Miller <9fans@hamnavoe.com> wrote:
> I've run it on a two-processor VIA vt310. An extra cpu does help with
> responsiveness.
Doesn't surprise me:
http://www.cs.wisc.edu/~kchak/papers/spin-pact06.pdf
If I skimmed this correctly, one thing I gleaned is that any time you
have more virtual CPUs than real CPUs (or cores, for you hyperthreaded
folks), you're going to take a measurable hit (duh). Oh, plus one
core/CPU, for the host OS.
So, your Xen setup on a dual-core chip should be very nice.
I also just came across:
http://www.hpl.hp.com/personal/Lucy_Cherkasova/papers/xenqos-mware-camera-ready.pdf
but haven't skimmed it yet.
-Jack
next prev parent reply other threads:[~2006-12-25 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 5:26 ron minnich
2006-12-24 9:30 ` Richard Miller
2006-12-25 1:00 ` Jack Johnson [this message]
2006-12-24 10:25 ` Harri Haataja
2006-12-24 17:15 ` David Leimbach
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=6e35c0620612241700h50fd3b0aw1d326216c9ae2c3b@mail.gmail.com \
--to=knapjack@gmail.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).