# Background task time different with same project but different instances **URL:** \ **Category:** SonarQube Server / Community Build\ **Tags:** java\ **Created:** [May 21, 2024, 6:30am UTC](https://community.sonarsource.com/t/background-task-time-different-with-same-project-but-different-instances/115659 "2024-05-21T06:30:08Z")\ **Posts on this page:** 1\ **Showing post:** 4
**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:** [May 27, 2024, 2:09pm UTC](https://community.sonarsource.com/t/background-task-time-different-with-same-project-but-different-instances/115659/4 "2024-05-27T14:09:54Z")
I’m not really sure what you’re referring to by `ttl`. The maintenance I’m referring to is essentially what’s outlined in this post: > [@SonarQube becomes slow after PostgreSQL upgrade](https://community.sonarsource.com/t/sonarqube-becomes-slow-after-postgresql-upgrade/37925): > > Hello SonarQube Operators! It’s common that after performing an upgrade of PostgreSQL, a SonarQube instance connected to a PostgreSQL database can become painfully slow. Thankfully, we know how the issue can usually be addressed (it works almost every time!): by executing the following command against your Postgres database. VACUUM FULL ANALYZE For a PostgreSQL database, a VACUUM FULL command reclaims unused storage, while the ANALYZE command updates statistics used by the planner to determi… --- _[View the full topic](https://community.sonarsource.com/t/background-task-time-different-with-same-project-but-different-instances/115659)._