References:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview :
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
Analyzed the logs the summary is as below :
Patch used for testing :
https://gerrit.onap.org/r/c/cps/+/129829/5//COMMIT_MSG
Configurations:
| # | Configuration | Description |
|---|---|---|
| 1 | Number of CPS Instance | 1 |
| 2 | Total number of threads to send each batch (Register cm handle) | 4 |
| 3 | Batch size | 100 |
| 4 | To register 1458 cm handles | Used to send 15 batchs (100 cm handles in each batch) |
| # | Watchdog | Fixed Delay String (in ms) |
|---|---|---|
| 1 | timers:
advised-modules-sync:
sleep-time-ms: | 30000 |
| 2 | timers:
locked-modules-sync:
sleep-time-ms: | 300000 |
| 3 | timers:
cm-handle-data-sync:
sleep-time-ms: | 30000 |
| # | Data Sync | Enabled ? |
|---|---|---|
| 1 | data-sync:
cache:
enabled: | false |