Performance testing

[tumbledwyer]

Description

A number of improvements to increase the performance of OpenCRVS events service:

Remove the wait_for when using the API

Every request waits for elasticsearch to index the changes before returning.
This is on an interval of once per second.
This is useful from the UI so that refresh only happens once elasticsearch is updated.
From a performance testing perspective, it makes it impossible to get real number.

Changed to wait_for on request from the client, API requests immediately return.

Improved Zod schema parsing

Code previously parsed all Zod schemas and then checked how many it parsed and then selected highest priority if the number of parse matches was greater than 1.

Changed to order schemas by priority and then parse until it found a match. Logic is equivalent but dramatically reduces amount of processing on every request.

Cache Admin Structure

Admin structure is requested on every write operation, multiple times.

Added a cache since this almost never changes. This was the biggest saving in the tests.

Remove repeat calls to getEventById

Multiple calls to getEventById in a single request. The event exists in ctx.event so does not need to be refetched.

Used ctx.event where possible and passed event as a parameter otherwise. There is still some possible further optimisation here.

Checklist

• I have linked the correct Github issue under "Development"
• I have tested the changes locally, and written appropriate tests
• I have tested beyond the happy path (e.g. edge cases, failure paths)
• I have updated the changelog with this change (if applicable)
• I have updated the GitHub issue status accordingly

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".

[github-actions]

ℹ️ Coverage metrics explained:
• Statements — Executed code statements (basic logic lines)
• Branches — Tested decision paths (if/else, switch, ternaries)
• Functions — Functions invoked during tests
• Lines — Source lines executed

[github-actions]

📊 commons test coverage

Statements: 75.5%
Branches:   39.93%
Functions:  56.78%
Lines:      75.09%
Updated at: Wed, 06 May 2026 12:18:09 GMT

[ocrvs-bot]

Your environment is deployed to https://performance-testing.e2e-k8s.opencrvs.dev

[Zangetsu101]

Awesome work. Just wondering would it be easier to maintain a events cache tied to the request's lifecycle instead of passing it around?

[Zangetsu101]

UUID or string?