Wed, 31 Mar 2010 09:57:18 +0200 [optimization] traced_selection is used very intensively in debug mode stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 09:57:18 +0200] rev 5094
[optimization] traced_selection is used very intensively in debug mode optimizing it is worth the pain. Basically : don't do stuff unnecessary when we don't trace anything.
Wed, 31 Mar 2010 09:55:19 +0200 [optimization] improve massive write performance by optimizing hooks selection stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 09:55:19 +0200] rev 5093
[optimization] improve massive write performance by optimizing hooks selection profiling on some massive deletion showed up that 2/3 of the time was spent in hooks selection. Those changes make it much more acceptable (through selection is still not negligeable): * use one registry for each event, so we've much less hooks to check when emiting an event as well as no more need for the match_event selector. This required ability to put one appobject into several registries, using a __registries__ class attribute. * check for deprecated .enabled at registry initialization time instead of at selection time A very simple HooksManager class has been reintroduce to choose the right registry on call_hooks. Those optimisations leads to a ~x3 factor of time necessary to delete 16000 entities.
Wed, 31 Mar 2010 09:45:14 +0200 [upgrade] after upgrade, fork command to start instance avoid grave uicfg pb (explicit rules all removed...) stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 09:45:14 +0200] rev 5092
[upgrade] after upgrade, fork command to start instance avoid grave uicfg pb (explicit rules all removed...)
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 tip