On 11/04/2015 12:10 PM, Jeremy Stanley wrote: > On 2015-11-04 08:43:27 -0600 (-0600), Matthew Thode wrote: >> On 11/04/2015 06:47 AM, Sean Dague wrote: > [...] >>> Is there a nodepool cache strategy where we could pre build these? A 25% >>> performance win comes out the other side if there is a strategy here. >> >> python wheel repo could help maybe? > > That's along the lines of how I expect we'd need to solve it. > Basically add a new DIB element to openstack-infra/project-config in > nodepool/elements (or extend the cache-devstack element already > there) to figure out which version(s) it needs to prebuild and then > populate a wheelhouse which can be leveraged by the jobs running on > the resulting diskimage. The test scripts in the > openstack/requirements repo may already have much of this logic > implemented for the purpose of testing that we can build sane wheels > of all our requirements. > > This of course misses situations where the requirements change and > the diskimages haven't been rebuilt or in jobs testing proposed > changes which explicitly alter these requirements, but could be > augmented by similar mechanisms in devstack itself to avoid building > them more than once.
Ok, so given that pip automatically builds a local wheel cache now when it installs this... is it as simple as https://review.openstack.org/#/c/241692/ ? -Sean -- Sean Dague http://dague.net __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
