On Wed, Nov 4, 2015 at 6:47 AM, Sean Dague <s...@dague.net> wrote: > I was spot checking the grenade multinode job to make sure it looks like > it was doing the correct thing. In doing so I found that ~15minutes of > it's hour long build time is compiling lxml and numpy 3 times each. > > I've always wondered why lxml is used rather than python's built-in XML support. Is there some function that xml.etree is missing that lxml.etree provides? The only thing I know about is that lxml has better support for some XPATH features.
:: Brant > Due to our exact calculations by upper-constraints.txt we ensure exactly > the right version of each of those in old & new & subnode (old). > > 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. > > -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 >
__________________________________________________________________________ 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
