# Compiling the project takes too long for a single job, Travis is timing out on me

**URL:** <https://travis-ci.community/t/compiling-the-project-takes-too-long-for-a-single-job-travis-is-timing-out-on-me/9981>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [September 24, 2020, 2:33am UTC](https://travis-ci.community/t/compiling-the-project-takes-too-long-for-a-single-job-travis-is-timing-out-on-me/9981 "2020-09-24T02:33:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [September 24, 2020, 11:24pm UTC](https://travis-ci.community/t/compiling-the-project-takes-too-long-for-a-single-job-travis-is-timing-out-on-me/9981/3 "2020-09-24T23:24:08Z")

</div>

As a side note, you should use `-j<ncpus>` for CPU-bound tasks like compilation. The common theory that it’s optimal to pass `<ncpus+1>` is not confirmed by experiment:

> <https://stackoverflow.com/questions/2499070/gnu-make-should-the-number-of-jobs-equal-the-number-of-cpu-cores-in-a-system>

---

_[View the full topic](https://travis-ci.community/t/compiling-the-project-takes-too-long-for-a-single-job-travis-is-timing-out-on-me/9981)._