From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: [9fans] the Thread War
Date: Mon, 12 Jul 2004 09:55:39 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0407120951280.28940-100000@maxroach.lanl.gov> (raw)
I hate to revive this but what the heck.
http://pl.atyp.us/misc/threads.tar.bz2
describes some thread microbenchmarks.
These two programs test context switch rates for threads. Usual
disclaimers apply about stupidity of microbenchmarks. But I'm curious to
see what those of you with 2.4 Ghz P4 boxes get.
No need to cc: Linus on this discussion.
ron
next reply other threads:[~2004-07-12 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 15:55 ron minnich [this message]
2004-07-12 16:49 ` andrey mirtchovski
2004-07-12 19:31 ` andrey mirtchovski
2004-07-12 19:39 ` boyd, rounin
2004-07-12 19:50 ` Micah Stetson
2004-07-12 20:07 ` andrey mirtchovski
2004-07-12 20:50 ` ron minnich
2004-07-12 21:45 ` andrey mirtchovski
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=Pine.LNX.4.44.0407120951280.28940-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--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).