From: Scott Schwartz schwartz@groucho.cse.psu.edu
Subject: Senseless benchmarks
Date: Mon, 28 Mar 1994 00:27:03 -0500 [thread overview]
Message-ID: <19940328052703.sqKrpZAe-1Nf0eB2fMy0Tce0J8glR5Shc34jSYDcKKc@z> (raw)
Just for fun, I ran the following program on a machine running SunOS and on a
machine running Plan 9 (with obvious alterations to get it to compile.)
I was hoping to see Plan 9 go faster, but they took about the same time
(10 seconds on a Sparcstation I). Has anyone done more thoughtful
benchmarks comparing the two kinds of systems?
/*
#include <u.h>
#include <libc.h>
#define exit exits
*/
main()
{
int i;
for (i=0; i<1000; ++i) {
if (fork()) {
wait(0);
} else {
exit(0);
}
}
}
P.S. reason #2 why plan 9 is not my favorite operating system "vc, xc, etc".
given that you will usually use an mkfile most of the time anyway,
why not name them something sensible like "sparc-cc, mips-cc, etc-cc"?
next reply other threads:[~1994-03-28 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-28 5:27 Scott [this message]
1994-03-28 5:49 Piers
1994-03-28 6:06 Scott
1994-03-28 7:52 David
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=19940328052703.sqKrpZAe-1Nf0eB2fMy0Tce0J8glR5Shc34jSYDcKKc@z \
--to=9fans@9fans.net \
/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).