From: forsyth@minster.york.ac.uk forsyth@minster.york.ac.uk
Subject: fork test
Date: Sun, 10 Apr 1994 16:42:52 -0400 [thread overview]
Message-ID: <19940410204252.91JgVHvW50AH6jD35sg66cyHSRfaXpF_iKaoYbRXpos@z> (raw)
i've just tried the 10,000 fork test on a Sparc Classic
unix
156.1 real 136.9 sys 13.5 user dynamically linked
58.7 real 50.4 sys 3.2 user statically linked, dynamically paged executable
58.8 real 51.1 sys 2.8 user statically linked, not dynamically paged image (-n)
plan 9
26.9 real 20.4 sys 0.8 user no need to choose
the sparc classic has tiny caches, and a sleazy implementation of the Reference MMU
(TLB context flushes are implemented as complete TLB flushes). i might revise the MMU code,
but i don't think it will help this test on this model of sparc. memmove might
be made faster, though; i haven't checked yet. i haven't got figures for the ss/10,
since that hardware is different again.
next reply other threads:[~1994-04-10 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-04-10 20:42 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-03-28 17:23 Erik
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=19940410204252.91JgVHvW50AH6jD35sg66cyHSRfaXpF_iKaoYbRXpos@z \
--to=forsyth@minster.york.ac.uk \
/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).