Follow-up from "GithubImporter: Optimize Pull Request MergedBy Importer"
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=344552) </details> <!--IssueSummary end--> The following discussion from !69478 should be addressed: - [ ] @dstull started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/69478#note_717758940): (+2 comments) > @alexbuijs can you please review the ~database? I don't think there is much db wise to review here, but all importers trigger db review. - Consider lowering the batch size of the `find_each` in `Gitlab::GithubImport::Importer:: PullRequestsMergedByImporter#each_object_to_import` to 500 to improve query speed. See original thread for analysis.
issue