tree 43024600814cc59a06275527bd82205e3809b450
parent abecc8e1951af2c1b334e05a439fd40450d8b4c3
author Saša Živkov <sasa.zivkov@sap.com> 1694170129 +0200
committer Saša Živkov <sasa.zivkov@sap.com> 1694171999 +0200

Use a shared heartbeat thread pool, don't create one for each lock

Before this change, each instance of the Lock class created a thread
pool of size one to run the heartbeat task. This didn't scale well as
the number of threads needed to maintain the heartbeat of N locks was N.
There are Git operations which lock a large number of refs and this
would have resulted in the large number of threads maintaining
heartbeat for each lock.

Now we use a dedicated thread pool of hardcoded size 10. We may make
this size configurable in the future if we see a need for that.

Change-Id: Ia657a7a7ab80c5124bba40981e79c281e7381f53