Suggestion:

• Implement a feature to configure a dedicated URL specifically for Git operations over HTTP which is separate from the instance base-url. (git-http base url)
• Currently, Bitbucket allows configuring a separate URL only for SSH using the "SSH Base URL."

Use-Case:

• In very large and busy instances, customers often use dedicated cluster nodes to manage SSH and HTTP traffic through separate load balancers.
• As almost all SSH traffic is for Git operations, this setup allows for an even distribution of Git requests among the SSH nodes.
• However, HTTP traffic includes a mix of Git, UI, and API requests.
• Most load balancers (like F5) use simple algorithms, like round-robin or least connections, to distribute traffic and cannot differentiate between resource-intensive Git requests and lighter UI/API requests. This can lead to scenarios where one node is overloaded with Git requests, while other nodes handle mostly UI or API requests despite having a similar number of connections.
• Additionally, because the load balancer gives equal weight to all incoming requests (git/UI/API), it is unable to distinguish and evenly distribute http Git requests across all nodes in the cluster.
• Having a separate, dedicated URL for Git operations over HTTP can address this issue by allowing customers to set up a dedicated load balancer specifically for Git traffic over http, similar to the configuration available for SSH.