IMA: getPastEvents sometimes work significantly slow as expected

[EvgeniyZZ]

Description
Case: compatibility check
IMA version 11/16: 2.0.0
IMA version 5/16: 1.5.0-beta.1
Skaled: the same for all - 3.16.1

Step to reproduce
Run transfers loop between schain
When processing message takes more than 60 seconds observe logs on working node

Actual result
In some regular use case search of IMA msg can takes more then 30-... min, depends on amount of blocks on the schain.
NOTE: Root cause investigate in progress

Expected result
IMA processing msg should not takes more than 40 seconds in average. getPastEvents should parse logs not longer than 5-7 seconds based on previous results, and results on nodes not affected by this problem.

NOTE: Look closer on logs, attention to PWA thread on affected chain.
Compare imaGPE_big.txt with imaIterativeScan13.txt and imaIterativeScan12.txt

imaGPE_big.txt
imaGPE.txt
imaIterativeScan12.txt
imaIS12.txt
imaIterativeScan13.txt
imaGPE13.txt

Tasks

Preview Give feedback

We're having trouble rendering your tasklist, it's most likely has one of the following formatting errors:

• indented tasks (i.e. nested tasklist; support for this is coming!)
• an empty task (i.e. - [ ] on a line by itself)
• any empty new lines (before/after the tasklist or in between tasks)
• duplicate issue/pr links
• a draft task exceeds 512 characters

Please check the tasklists documentation for more information. 🔗 Feedback Discussion

Thank you for participating in the Private Beta ❤️

No tasks being tracked yet.

Tasks

Preview Give feedback

1. OutgoingMessage event not found on first iteration of search #1554
   bug epic:ima-optimizations +2
   

[EvgeniyZZ]

Verified: Can't reproduce.
IMA Agent: 2.0.1