Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize /v2/syncDetails, by improving location entities isEntityChanged() calls #809

Open
himeshr opened this issue Oct 17, 2024 · 0 comments

Comments

@himeshr
Copy link
Contributor

himeshr commented Oct 17, 2024

Motivation

WebTransaction/SpringController/v2/syncDetails (POST) call does not seem to have improved with the fix done as part of
#798

We see through trace that currently, following 2 invocations are costly and are good candidates for the Removal of RLS and query invocation approach.

  • LocationRepository.isEntityChanged(SyncParameters syncParameters);
  • LocationMappingRepository.isEntityChanged(SyncParameters syncParameters);

Acceptance Criteria

Optimize /v2/syncDetails (POST) call, by removing RLS during invocation of

  • LocationRepository.isEntityChanged(SyncParameters syncParameters);
  • LocationMappingRepository.isEntityChanged(SyncParameters syncParameters);

Ensure performance impact is not shifted to any other place in the same call.

@github-project-automation github-project-automation bot moved this to New Issues in Avni Product Oct 17, 2024
@himeshr himeshr moved this from New Issues to Focus Items in Avni Product Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Focus Items
Development

No branches or pull requests

1 participant