From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from vultr.musolino.id.au ([45.76.123.158]) by ewsd; Tue Mar 10 20:12:04 EDT 2020
Message-ID: <086912A0EAF35F67FD36D1DF0B200DD2@musolino.id.au>
From: Alex Musolino <alex@musolino.id.au>
Date: Wed, 11 Mar 2020 11:11:24 +1100
To: 9front@9front.org
Subject: Re: [9front] Bug in time cmd?
In-Reply-To: 528d3ca3-2d46-77a8-a367-ffac684bd88c@qs.co.nz
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: cache software-scale control 

These figures come from the Waitmsg structure returned by wait(2).  The
'u' time is the total user time of the child process *and descendants*.
Given that you likely have a multiprocessor and mk will parallelise its
work according to the NPROC environemnt variable, that ought to explain
how you are able to achieve 14s of user time in only 6s real time.