CPS-2478: Module Sync Inefficiencies

Calls to DB for modules (check existing Tag)

Could easily cache Module Set Tag in memory to reduce this

@Toine Siebelink Nov 18, 2024 Implemented as part of https://gerrit.onap.org/r/c/cps/+/139344

First batch (on each thread) calls to DMI for same Tag

Use cache from #1 or store first cm Handle in DB immediately instead of as part of Batch

@Toine Siebelink Nov 18, 2024 PoC-ed as part of https://gerrit.onap.org/r/c/cps/+/139344 but then replaced with Distributed Hazelcast Set instead

Store new schema set for each cm handle (instead of Tag)

Use schema set concept (in CPS Core) to only store each new Module Set Tag once. This seems the correct usage of Schema Set concept and wil have the greatest performance benefit. This requires more costly and difficult solution as NCMP code is develop assuming each cm handle schema set name is the same as its id.
Affected use-cases:

1. Initial Registration

2. Upgrade

@Toine Siebelink Nov 18, 2024 No considered as part of this User Story. Create a new Technical Debt Jira instead: CPS-2506: Use ModuleSetTag for SchemaSet Names during NCMP registrationOpen

Cm Handles

500

Module Set Tags

2

250 CM Handles Each

Worker Threads (parallelism)

2

Environment

Windows 11. 13th Gen Intel(R) Core(TM) i9-13900H 2.60 GHz

# Calls

# Calls

500

2

Used ‘privateModuleSetCache’ map to locally store required data on each thread. Data discarded when thread finishes but this eliminates vast majority of DB calls.

100-200

2

Use a Hazelcast distributed Set: ‘moduleSetTagsBeingProcessed’ to prevent multiple threads/instances attempting to process the same new tag.

500

500

2 x faster. Probably due to less contention with read queries

5+

5+

1.7 x faster

> 2 x faster!

Time Spent (ms)

Time Spent (ms)

%

5

0%

2,667

1%

add 200ms delay for first 10 batch of 100

206,220

85%

33,313

14%

242,205

~4m3s

Need to add 2 minutes for initial delay: ~6m ~ 55 CM Handles/sec