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.

Sign up for GitHub

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

Jump to bottom

Determine if the limit query optimizes performance in calculateMissedAndInsert #546

Closed
nullpointer0x00 opened this issue Sep 17, 2024 · 1 comment
Closed

Determine if the limit query optimizes performance in calculateMissedAndInsert #546

nullpointer0x00 opened this issue Sep 17, 2024 · 1 comment

Comments

@nullpointer0x00
Copy link
Contributor

Summary

Determine if the limit query optimizes performance in calculateMissedAndInsert by tracking execution times. If successful, remove the warning.

Problem Definition

The warning was added to monitor if applying a limit to database queries resolves inefficiencies in calculateMissedAndInsert. The method had been taking over 1000ms to execute due to fetching and serializing large data sets, causing performance issues.

Proposal

Monitor the performance improvements and remove the warning if the issue is resolved.
PR: #544
@nullpointer0x00
Copy link
Contributor Author

We removed all this code completely with #548.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nullpointer0x00