From: ori@eigenstate.org
To: plan9fullfrontal@qs.co.nz, 9front@9front.org
Subject: Re: [9front] Bug in time cmd?
Date: Tue, 10 Mar 2020 21:45:37 -0700 [thread overview]
Message-ID: <D6AD832EEAFE0C23FBD7DFBA68F8F61B@eigenstate.org> (raw)
In-Reply-To: <c7cd60b0-508f-c57d-bfd0-99c138e74d88@qs.co.nz>
> Only across two cpus. I only have one cpu running plan9. So it is 8cores
> 16 threads. How you count cores I stopped trying to figure out long
> ago. Even assuming threads added no time saving, then 8 -> 2 is still
> poor utilization. Under Linux , core threads make a measurable
> difference to performance.
Sure. It's not surprising that there's room for improvement,
though only a 2x speedup on a 8 core/16 thread machine is
mildly surprising.
You said you were using ramfs. Ramfs is dead simple, mostly
for private/scratch storage, not for performance. The kernel
itself likely has some highly contendend locks, like malloc
and runqueue locks.
next prev parent reply other threads:[~2020-03-11 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 0:11 Alex Musolino
2020-03-11 2:28 ` Trevor Higgins
2020-03-11 2:33 ` ori
2020-03-11 4:15 ` Trevor Higgins
2020-03-11 4:45 ` ori [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-10 23:39 Trevor Higgins
2020-03-13 16:55 ` [9front] " 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=D6AD832EEAFE0C23FBD7DFBA68F8F61B@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=plan9fullfrontal@qs.co.nz \
/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).