On 15 September 2014 13:30, Tim Harder <radher...@gentoo.org> wrote: > I haven't run portage metadata regen on a beefy machine lately, but I > don't think it could keep up in all cases. Perhaps someone can prove me > wrong. > > Anyway, things could definitely be sped up if portage merges a few speed > tweaks used in pkgcore. Specifically, I think using some of the weakref > and perhaps jitted attrs support along with the eclass caching hacks > would give a 2-4x metadata regen speedup. Otherwise pkgcore could > potentially be used to regen metadata as well or some other tuned regen > tool. >
I generate metadata for the perl-experimental overlay periodically as a snapshotted variation of the same, and the performance isn't so bad. However, what I suspect you *could* do with a push hook is regen metadata for only things that were modified in that commit, because I believe there's a way to regen metadata for only specific files now. ie: modifications to cat/PN *would* trigger a metadata update, but only for that cat/PN modifications to eclass/* would *NOT* trigger a metadata update as part of the push. And doing tree-wide "an eclass was changed" updates could be done with lower priority in an asynchronous cron job or something so as not to block workflow for several minutes/hours/whatever while some muppet sits there watching "git push" do nothing. -- Kent *KENTNL* - https://metacpan.org/author/KENTNL
