[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.

     1

<?xml version="1.0" encoding="UTF-8"?>

     2

     3

<display window-flags="sticky, below" width="185" height="200">

     4

     5

	<sensor id="r" module="rqlsensor"/>

     6

        <sensor id="FS" module="FontSelector,1,Sans 10  black"/>

     7

     8

	<!-- left border -->

     9

	<group x="0" width="5" height="200" bg-uri="gfx/border-left.png"/>

    10

    11

	<image x="10" y="0" uri="gfx/logo_erudi.png"/>

    12

    13

        <array id="results" x="10" y="30"

    14

               watch="layout=r:layout, length=r:length">

    15

	  <label id="lbls1" color="black"

    16

		 on-enter="r:enter-line"

    17

		 on-leave="r:leave-line"  

    18

		 on-click="r:click-line"

    19

  		 watch="value=r:result, font=FS:font0, color=r:resultbg"/>

    20

        </array>

    21

    22

</display>