Stephen Smoogen wrote:
> 1. Drive size is not just what is needed but also throughput. The large
> drives needed to store the data COPR uses for its hundreds of chroots are
> much 'slower' on reads and writes even when adding in layers of RAID 1+0.
> Faster drives are possible but the price goes up considerably.
> 2. Throughput of individual drives also requires backplane speeds which
> match peek throughput of all the drives. Otherwise you end up with lots of
> weird stalling (as seen on certain builders which have such drives).
What kind of throughput is needed for a repository that has not seen any new
builds for 2 years? Such a repository is going get only a handful downloads
and no uploads. Instead of deleting old repositories, they can be moved to a
low-throughput archive storage. This can be made transparent through
symlinks, union file systems, or even just at the HTTPS level if Copr itself
knows how to unarchive a repository when internally needed (e.g., if a new
build is submitted after 2 years of inactivity).
Kevin Kofler
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
