<!--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=334021) </details> <!--IssueSummary end--> The following discussion from !64256 should be addressed: - [ ] @mkaeppler started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/64256#note_604716263): > I'm not super well versed in Redis specifics, but I'm always suspicious of doing synchronous I/O in loops. This is performing a Redis roundtrip `n` times sequentially but does not depend on the loop variable. I would check how many times we might be doing this here (max) as a function of collection length (also: how often we enter this loop!) > > Redis supports [pipelining](https://redis.io/topics/pipelining) which allows for more efficient use of the client connection when many operations needs to be performed and can run in parallel i.e. without waiting for a response. Looks like we don't have an API for `ObjectCounter` yet that can perform a pipelined `incr`. Maybe we can add this in a follow-up?