We're experiencing continuous crashes with our Bitbucket server that seem to be caused by excessive memory utilization during several Git operations such as git clone, git pull, git push, among others.

I have been running numerous load tests and have been able to consistently recreate the issue. The excessive memory usage triggers the Out of Memory (OOM) killer in our Bitbucket instance, leading to an undesired restart of the service. Our Bitbucket is running on an AWS EC2 c6a.2xlarge instance with 16GB memory, and the crashes happen when executing the load test scripts from both the Jenkins agent and two additional machines.

I've already tried implementing throttling settings in the bitbucket.properties configuration file to alleviate the CPU usage, but this appears to have had no effect on limiting memory usage. Additionally, I attempted to modify the JVM settings by raising the maximum allowed memory to 10GB, but this also had no impact on resolving the issue.

From your official documentation, I understand that the memory utilization of Git operations isn't managed by the standard memory settings in the _start-webapp.sh file, as Git processes are handled outside of the JVM. Given this, could you please provide me with guidance or any available solutions which can help to restrict the memory usage resulting from Git related operations in Bitbucket?

https://confluence.atlassian.com/bitbucketserver/scaling-bitbucket-server-776640073.html#ScalingBitbucketDataCenter-Memory

Your assistance in mitigating this ongoing problem would be greatly appreciated.