>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1618232. --> Reported by: [jhodgdon](https://www.drupal.org/user/155601) >>> <p>I think that if we get into a situation where we have a lot of branches/projects on api.drupal.org, the API module will need to be more intelligent about how it checks branches for updates.</p> <p>My plan is that instead of checking all files branches for updates each cron run, we'll have the ability to throttle them down (like you can now for the PHP branches). And instead of just running all the updates directly, we'll use a queue for updating branches, so we don't spend all of our cron time (or run out of cron time) just running the check for new/updated files.</p> <p>I'm actually already working on this in conjunction with restructuring the project/branch database structure in<br> <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/api/issues/990108" title="Status: Closed (fixed)">#990108: Links and search do not make sense and are not working across projects</a></span></p>