El mar, 19-11-2019 a las 00:21 +0000, Sergei Trofimovich escribió: > repoman slows down ~linearly with amount of profiles being scanned. > In case of amd64 we have 28 stable profiles. > > To speed up processing and fit into time budged of various CIs we can > split the work across different processes that handle different profiles. > > Example benchmark on ::haskell overlay: > $ ./repoman full --include-arches=amd64 > ~65 minutes > $ ./repoman full --include-profiles=default/linux/amd64/17.0 > ~4 minutes > This allows for a crude sharding of work across processes and allows for > cheap tree-wide scans for early failures. >
Just for knowing (as I guess there is a technical issue preventing that), why repoman is not trying to check one profile per core in parallel by default by itself? Thanks a lot for the info :)
signature.asc
Description: This is a digitally signed message part
