Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixer needs to scale better given the growing number of bundles in Clear #558

Closed
gtkramer opened this issue Mar 18, 2019 · 1 comment
Closed

Comments

@gtkramer
Copy link

gtkramer commented Mar 18, 2019

As of one month ago for 27760, mixer build bundles took 19 minutes or so. Today, mixer build bundles for 28350 takes 41 minutes or so. Given we've more than doubled content in the distro, we've seen roughly linear growth. However, we've also come to better understand the overhead of using mixer. For comparison, doing just a dnf install of all bundles manually for the same build one month ago took around 11 minutes and today takes around 19 minutes. This is to start and track a discussion around what can be done to help DevOps to continue iterating quickly.

One possible piece to the solution could be to remove all duplicate provides for our RPM repository. This would make our RPM repository deterministic so that dnf would never need to pick one package over another. Then a single dnf install could be performed by mixer to create the chroot rather than 843.

As suggested by @bryteise, there may be ways to parse the repodata directly rather than relying on dnf to reduce metadata gathering times.

@gtkramer
Copy link
Author

Closing, obsoleted by #630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant