From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 3/3] .travis.yml: make -j3
Date: Mon, 4 Apr 2016 18:45:45 +0100 [thread overview]
Message-ID: <1459791945-4985-4-git-send-email-alex.bennee@linaro.org> (raw)
In-Reply-To: <1459791945-4985-1-git-send-email-alex.bennee@linaro.org>
The move from Travis VMs to Containers came with a upgrade from 1.5
cores to 2. The received wisdom is -j N+1 means a core can be doing work
while other threads wait for IO to complete. This is hard to test on the
Travis infrastructure but an initial before/after eyeballing seems to
confirm it is an improvement.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index f02710d..50ac17f 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -60,7 +60,7 @@ before_install:
before_script:
- ./configure ${CONFIG}
script:
- - make -j2 && ${TEST_CMD}
+ - make -j3 && ${TEST_CMD}
matrix:
include:
# Sparse is GCC only
--
2.7.4
next prev parent reply other threads:[~2016-04-04 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 17:45 [Qemu-devel] [PULL 0/3] Travis updates Alex Bennée
2016-04-04 17:45 ` [Qemu-devel] [PULL 1/3] .travis.yml: collapse the test matrix Alex Bennée
2016-04-04 17:45 ` [Qemu-devel] [PULL 2/3] .travis.yml: enable OSX builds Alex Bennée
2016-04-04 17:45 ` Alex Bennée [this message]
2016-04-05 8:06 ` [Qemu-devel] [PULL 0/3] Travis updates Peter Maydell
2016-04-05 8:45 ` Alex Bennée
2016-04-05 9:17 ` [Qemu-devel] [PULL v2 0/3] Travis updates (without changelog entries) Alex Bennée
2016-04-05 10:03 ` Peter Maydell
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=1459791945-4985-4-git-send-email-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).