thanks for your answer and clarification, and you guessed correctly
Indeed branches have changed a lot between 7.9 and 8.9, and with the removal of the short-lived branch specific implementation, all of the code from each branch last analysis is now stored in DB, and in this table specifically.
There is no easy way to predict the DB impact for all SonarQube users, e.g. it is not expected to impact the majority of users relying mostly on PR analysis in their development flow.
Also a larger DB may not be a problem:
- it is not expected to impact your DB or SonarQube performances much, SonarQube data model was designed for this and the additional written data is not expected to be read more.
- DB size, related to this change, should peak after the sonar.dbcleaner.daysBeforeDeletingInactiveBranchesAndPRs period is reached (30 days per default), then it should be stable. In your case DB size would probably have stabilized, and resumed its previous average growth, around 100GB.
Decreasing the sonar.dbcleaner.daysBeforeDeletingInactiveBranchesAndPRs housekeeping parameter to 7 days has probably not improved IOPS or CPU usage much on your DB instance(?), it shrunk its size though.
Keeping a feature branch analysis for more than 7 days is probably rarely needed, but in case it would be, you may allow more than 7 days for it, with additional costs only bound to the increased DB storage.