Review test coverage for I/O
It's been called out recently that since we're not currently seeing Gitaly being stressed in terms of I/O that we may have a gap in test coverage.
We currently have a slate of tests that cover a good range of popular API endpoints along with some Web and Git tests. The aim of the tool is to perform the same actions as a user might at scale so we don't have any specific Gitaly tests by design but this task is to explore any user actions that we know for a fact cause heavy Gitaly I/O operations.
A possible factor may be repo size. We assumed at the beginning that gitlab-ce
was a large repo and built our testing around that but now understand it to be not really large in the grand scheme of things. It's still a good median repo for us though that contains a lot of realistic data and imports in a relatively short time (~30 mins).