Open Stack

On 10/30/2012 07:07 PM, Doug Hellmann wrote:
<snip>
 >     While I get that in production, the class loading will disappear in
>     the noise, that huge hit on the unit tests seems really problematic
>     from a developer point of view. And a big problem from a CI
>     perspective. Anyone have ideas on why this is such a huge hit, or
>     thoughts on how to mitigate it?
>
>
> I haven't profiled it, but my guess is that the extra time is from
> scanning the entrypoints registry. That would, as you say, hardly matter
> when it is only done once on startup. Perhaps we need to cache driver
> loaded from the config outside of the manager (?) instance where it is
> used to avoid having to rescan the registry each time the tests set up
> the manager.

Given that in our use case we already know the one class we are loading, 
is there any reason all the entrypoints are being scanned anyway? That 
just seems wasteful. And it also seems like it only gets worse as the 
entrypoint list grows.

As the stevedore author, could you add fast path loading into the 
library, and fail back to the full scan if something goes wrong on that?

	-Sean

-- 
Sean Dague
IBM Linux Technology Center
email: sdague at linux.vnet.ibm.com
alt-email: sldague at us.ibm.com