From: Giacomo Tesio <giacomo@tesio.it>
To: 9front@9front.org
Subject: strange stats
Date: Tue, 24 Feb 2015 18:10:50 +0100 [thread overview]
Message-ID: <CAHL7psFc=-Dcxivp1kuAw3B1j3=Qk+izcpWCK01FyGsKNgBRUw@mail.gmail.com> (raw)
Hi, I've noted a strange behaviour in stats during the system compilation.
When I run `mk install` at the rio terminal, stats shows that load,
context and syscalls grow to 100% untill the window buffer is full and
then go down to the previous values. If I scroll down the window, the
stats grow up again until the the window is full, than drop again.
Instead if I send stdout to a file, that stats remain 100% till the
compilation completes.
Such behaviour makes me wonder if writing logs to the console is
blocking the compiler.
Is this the expected behaviour?
Moreover, does the compiler benefit from multiple cores?
`xl top` at xen dom0 shows the cpu usage of the 9front vm at 112% but
I did expect it around 400%, since I assigned 4 cores to the system.
Giacomo
next reply other threads:[~2015-02-24 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:10 Giacomo Tesio [this message]
2015-02-24 17:24 ` [9front] " cinap_lenrek
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='CAHL7psFc=-Dcxivp1kuAw3B1j3=Qk+izcpWCK01FyGsKNgBRUw@mail.gmail.com' \
--to=giacomo@tesio.it \
--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).