From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] ftq on 9front: astoundingly good
Date: Tue, 11 Feb 2025 08:45:01 -0800 [thread overview]
Message-ID: <CAP6exY+aKiN4r0813nqsEm=mAYZCtqEGDjenSBP0_WACLr=_Zg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
btw, I just ran ftq on t420 on 9front. ftq has the option to wire to a
core: I wired to core 2.
This is a full desktop, with rio, wifi stack, and so on.
The results from ftq on 9front are mindboggling. One simple figure of
merit we now develop is "if I had all the machine all the time, how much
would I get?"
ftq prints "how much did I get as a fraction of how much could I get?"
It is never 1. It is rarely .98. On VMs it sits around .91. There's always
interference
On 9front, wired to core 2, it is .994. This shocked me.
The amount of careful finagling you have to do on linux to get close to
this number is ... a lot.
And even on the almost-fastest-machine in the world, Frontier, they still
have to work hard to quiet the OS environment down.
Also, sadly, right now, on NIX, the AC run I just did only gets .976, so ..
I need to look a bit more. It used to be much better, but this could be a
flaw in the port.
It will be interesting to see if grap can handle 1/2 million data points.
So far, acme struggles with this file. ed just says ?TMP
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tb8c8d6c502962279-M293b0f2409ff296b6258d53b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2021 bytes --]
reply other threads:[~2025-02-11 16:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAP6exY+aKiN4r0813nqsEm=mAYZCtqEGDjenSBP0_WACLr=_Zg@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=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).