Issue Summary

• Customer has over 4k branches in a migrated repository, this is resulting in API 500/504 timeouts

This is reproducible on Data Center: no

Steps to Reproduce

1. Have a large repository with many files and many branches
2. Attempt to view commits/branches and encounter timeout error

Expected Results

• There is no formal branch limitation, so this should render in the UI without issues

Actual Results

• The API appears to struggle when there are thousands of branches present in the repository

Workaround

• Performing a branch cleanup to reduce the number of branches/commits, this can be a timely process however and the performance issues should be investigated wholesale