Hi @alexander.kitaev ,
I have tried in other way. Cloned the repo to local and from there fetched the git for-each-ref command output. The command executed without any delay and reports the references count as 4512 mentioned below.
$ git for-each-ref | wc -l
4512
Hello Venkat,
I think that number of references might indeed affect translation performance. It looks like the other issue you experience (long time to import 2gb repository) is also related to the extremely slow shared filesystem access times.
We had never experienced these sort of behaviour before.
Bitbucket stores its repositories on the NFS share so now I’m more or less convienced that those delays (up to 30 minutes for a simple operation) are somehow related to the NFS access. I wonder if there are any logs from the NFS that might sched some light on what could be the root of the problem?