CmHandle creation performance degradation

Current behavior
 
I saw there is an ongoing implementation (in frame of notification handling) around cmHandle registration which will change the way it worked before, I mean the newly introduced states and the way how NCMP gets the modules.
I tried the CPS master as there are several bug corrections which is needed by us. During the cmHandle registration I saw that it is changed now.
 
With previous versions we were able to register 10k cmhandles (in 4 threads) in 12 minutes.
With the current CPS master we sent the 10k cmHandles  around 10 minutes to NCMP, so it is not faster than before. What I see is that NCMP starts getting modules in a background thread (seems to be one thread) and handling one cmhandle takes more seconds.
Currenlty in 12 minutes only 150 cmHandles got available with ready state in NCMP, because getting modules and changing the state is quite slow this way. 

Expected behavior
With previous versions we were able to register 10k cmhandles (in 4 threads) in 12 minutes.

Reproduction

Register huge amount of cmhandles and try to search them.
After 12 minutes there were only ~150cmHandles inready state
 

CPS version

https://gerrit.onap.org/r/gitweb?p=cps.git;a=commit;h=7914c8924723092345e8b4d829f15d2a3a5c72c8

Collected logs
NA