<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<html lang="en">
<head>
<meta content="text/html; charset=US-ASCII" http-equiv="Content-Type">
<title>
GitLab
</title>
<style>img {
max-width: 100%; height: auto;
}
</style>
</head>
<body>
<div class="content">
<p style="color: #777777;">
<a href="https://gitlab.com/rockdaboot">Tim Rühsen</a>
commented:
</p>
<div style="">
<p dir="auto">Well, just give it a try :-)</p>
<p dir="auto">My thoughts: since we only have one CPU core in a CI, -j2 makes sense for CPU intensive jobs with slightly I/O - like for compiling and linking. Since our test suite often waits with 0% CPU, a slightly larger value would be better. I tried -j10 just as a quick shot. -j4 or -j5 is likely better since with too many parallel CPU intensive processes we might see avoidable cache misses which even slow down the overall time.</p>
<p dir="auto">You can checkout / clone branch <code>tmp-ci-parallel-tests</code> from <a href="https://gitlab.com/rockdaboot/gnutls.git">https://gitlab.com/rockdaboot/gnutls.git</a>, change the values and push it.</p>
</div>
</div>
<div class="footer" style="margin-top: 10px;">
<p style="font-size: small; color: #777;">
—
<br>
Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/issues/897#note_266982680">view it on GitLab</a>.
<br>
You're receiving this email because of your account on gitlab.com.
If you'd like to receive fewer emails, you can
<a href="https://gitlab.com/sent_notifications/18cc9d35f23fcbb27800d0bb32256e5c/unsubscribe">unsubscribe</a>
from this thread or
adjust your notification settings.
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Issue","url":"https://gitlab.com/gnutls/gnutls/issues/897#note_266982680"}}</script>
</p>
</div>
</body>
</html>