<!--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=372051) </details> <!--IssueSummary end--> ### Problem The search for tags is implemented in the Rails application. That means that we have [to request all tags from the Gitaly](https://gitlab.com/gitlab-org/gitaly/blob/7750e95b0c1642eba9e325cf2dffbdd25b37c928/internal/gitaly/service/ref/find_all_tags.go#L42) and then [select matching tags](https://gitlab.com/gitlab-org/gitlab/blob/4df61fa75c5f32c793905a04c7cf7794a573003a/app/finders/tags_finder.rb#L11) from the result. It affects the performance of [the Tags API](https://docs.gitlab.com/ee/api/tags.html#list-project-repository-tags). Related issue for branches: https://gitlab.com/gitlab-org/gitlab/-/issues/372053+ ### Solution 1. Extend Gitaly code [to support search patterns](https://gitlab.com/gitlab-org/gitlab/blob/4df61fa75c5f32c793905a04c7cf7794a573003a/app/finders/git_refs_finder.rb#L21-33) from Rails 2. Send search parameter to the Gitaly instead of performing the search on Rails side.