From: Trevor Higgins <plan9fullfrontal@qs.co.nz>
To: 9front@9front.org
Subject: Some SMP performance measurements.
Date: Thu, 12 Mar 2020 15:38:34 +1300 [thread overview]
Message-ID: <03e5fb90-cee6-8c3a-3700-e547a2959e1e@qs.co.nz> (raw)
Using 'mk' just because it is there and manages the multitasking for
me. I used timing of a build to measure performance.
Comparing a standard build from ramfs with both source objects files in
the same file service , and a build where the source and object files
were split between 8 ramfs mount points.
I have found that the Fileservices are a significant source of
throttling of performance. Performance using hjfs shows ramfs is not
causing unexpected delay and ramfs always shows significant increase in
performance over hjfs.
Splitting the build directories showed a 4 fold decrease in real build
time with fewer processors/threads.
For a build with a single FS serving the source and a single FS serving
the object storage, there is no real saving in time after 4 threads. The
build process is completely IO bound with 6 threads.
The split build is IO bound with 8 threads but with better utilization
resulting in substantially lower build times.
No criticism of Plan9 or anything or anyone, just looking at the numbers
to help figure out how to design some software I am writing. SMP may not
be much use to me in my application.
--
We need another plan
next reply other threads:[~2020-03-12 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 2:38 Trevor Higgins [this message]
2020-03-12 12:14 ` [9front] " Steve Simon
2020-03-12 17:14 ` hiro
2020-03-13 16:52 ` Ethan Gardener
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=03e5fb90-cee6-8c3a-3700-e547a2959e1e@qs.co.nz \
--to=plan9fullfrontal@qs.co.nz \
--cc=9front@9front.org \
/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).