On Sat, Jun 13, 2020 at 6:14 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
On Fri, Jun 05, 2020 at 02:12:51PM -0600, Ken Dreyer wrote:
> If we had a "koji benchmark" tool, what would you like it to do?
> I've written an Ansible playbook that automatically sets up Koji
> according to our documentation, and I want to exercise the hub to see
> how it performs. We can use a benchmark tool to understand changes
> that could impact performance. As one example, we probably want to
> compare CentOS 7, 8, and Fedora.
Are you looking to just test the hub? Or also builders?
And a lot of this will depend on the database... and the builders and
the storage speed, etc.
You're right. Thanks to everyone who responded so far! This made me
realize I should think a little bigger here. Originally I was just
thinking about benchmarking the hub alone because there are a lot of
things to measure and improve there (like mass-tagging), but several
of the responses made me think it makes sense to track more processes
For example, SRPM generation would require dist-git and it's related
to how efficiently we perform Git operations. Off the top of my head,
the Koji SCM class simply runs "git clone -n", and we could probably
change that to always run shallow clones instead so that we're not
fetching so much history and unrelated branches.
Image generation is another important one, because it would implicitly
test compatibility and performance of qemu and docker (eventually