This ticket is being created from two sources:
The pattern observed by support is the following:
- persist issues step is the costliest step
- Primo analysis creates and stores 1.9 millions issues, persist issues step takes 1640214ms.
- Second analysis inserts 7942 issues and updates 31138 issues, persist issues step takes 1182291ms, ie. 72% of the time of the step during the primo analysis.
Similar situations have been observed by support on peach on project is LOC and issue size similar to the customer's project.
Persist issue step uses a batch session to reduce the number of network round trips to the DB.
While the batch session is efficiently leveraged during primo analysis as only inserts are performed, this is not the case at all during next analysis where inserts and updates are mixed.
On top of it, a bug has been observed, tracked in