From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Bug in time cmd?
Date: Fri, 13 Mar 2020 16:55:11 +0000 [thread overview]
Message-ID: <3a9787aa-4b57-4b39-bc92-8344fdd3972a@www.fastmail.com> (raw)
In-Reply-To: <528d3ca3-2d46-77a8-a367-ffac684bd88c@qs.co.nz>
On Tue, Mar 10, 2020, at 11:39 PM, Trevor Higgins wrote:
> Doing some timing tests with mk I got these sort of figures?
>
> 14.28u 6.14s 5.92r
>
> From my *nix understanding the 'u' time is way off. Actual elapsed time
> was approx 6seconds.
Haha! I wonder, could it be counting CPU time per core?
next prev parent reply other threads:[~2020-03-13 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 23:39 Trevor Higgins
2020-03-13 16:55 ` Ethan Gardener [this message]
2020-03-11 0:11 [9front] " 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
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=3a9787aa-4b57-4b39-bc92-8344fdd3972a@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).