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
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.
The fedora koji db is public, so you're welcome to use that, but
not sure it's a 'common' case. :)
What scalability problems have you encountered with Koji in the wild?
I'm thinking of things like:
- Tagging thousands of builds quickly
- Contention on the sessions table
- Maintaining thousands of builders
- Ensuring kojira runs in a timely manner
- tons of side tags, how long to newrepo them all
- patalogical packages like texlive hitting timeouts uploading, etc.
- writing out signatures of a ton of packages.
- response time for various web pages on the hub?
When we have test data, even if the benchmarks are fairly synthetic,
it's easier to see the impact of code changes before we ship.