# Splitting SonarQube job in multiple parts

**URL:** <https://community.sonarsource.com/t/splitting-sonarqube-job-in-multiple-parts/118332>\
**Category:** SonarQube Server / Community Build\
**Created:** [July 3, 2024, 2:17pm UTC](https://community.sonarsource.com/t/splitting-sonarqube-job-in-multiple-parts/118332 "2024-07-03T14:17:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [July 5, 2024, 2:41pm UTC](https://community.sonarsource.com/t/splitting-sonarqube-job-in-multiple-parts/118332/4 "2024-07-05T14:41:31Z")

</div>

Thanks! I think there’s two things worth investigating:

- Where is most of the time being spent on the scanner-side analysis. [See this post for advice](https://community.sonarsource.com/t/need-suggestions-on-speeding-up-sonar/116237/4)
- Where is most of the time being spent on server-side analysis? You can check [the _ce.log_ file](https://docs.sonarsource.com/sonarqube/latest/setup-and-upgrade/troubleshooting/).
- I see you’re using Postgres, are you regularly performing a [`VACUUM FULL ANALYZE`](https://community.sonarsource.com/t/sonarqube-becomes-slow-after-postgresql-upgrade/37925)?

---

_[View the full topic](https://community.sonarsource.com/t/splitting-sonarqube-job-in-multiple-parts/118332)._