qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, "Alex Bennée" <alex.bennee@linaro.org>,
	david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH v1 3/3] .travis.yml: make -j3
Date: Tue, 22 Mar 2016 12:53:15 +0000	[thread overview]
Message-ID: <1458651195-21176-4-git-send-email-alex.bennee@linaro.org> (raw)
In-Reply-To: <1458651195-21176-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>
---
 .travis.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.travis.yml b/.travis.yml
index 3f77bfa..345e3ca 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -59,7 +59,7 @@ before_install:
 before_script:
   - ./configure ${CONFIG}
 script:
-  - make -j2 && ${TEST_CMD}
+  - make -j3 && ${TEST_CMD}
 matrix:
   include:
     # Sparse is GCC only
-- 
2.7.3

  parent reply	other threads:[~2016-03-22 12:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 12:53 [Qemu-devel] [PATCH v1 0/3] reduce the matrix, add OSX, speed-up Travis? Alex Bennée
2016-03-22 12:53 ` [Qemu-devel] [PATCH v1 1/3] .travis.yml: collapse the test matrix Alex Bennée
2016-03-23  0:42   ` David Gibson
2016-03-22 12:53 ` [Qemu-devel] [PATCH v1 2/3] .travis.yml: enable OSX builds Alex Bennée
2016-03-22 13:49   ` Peter Maydell
2016-03-22 14:12     ` Alex Bennée
2016-03-22 12:53 ` Alex Bennée [this message]
2016-03-23  1:25   ` [Qemu-devel] [PATCH v1 3/3] .travis.yml: make -j3 David Gibson

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=1458651195-21176-4-git-send-email-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=david@gibson.dropbear.id.au \
    --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).