-
Notifications
You must be signed in to change notification settings - Fork 502
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
Diagnose DB spike issue #4382
Labels
Comments
sreuland
assigned sreuland, 2opremio, Shaptic, paulbellamy, sydneynotthecity, tamirms and erika-sdf
May 19, 2022
sreuland
added a commit
to sreuland/go
that referenced
this issue
May 24, 2022
…IT depending on whether paging cursor parameters are present or not
I suspect #4402 will help with client-side timeout enforcement when the db is unresponsive. |
sreuland
added a commit
to sreuland/go
that referenced
this issue
May 24, 2022
…ce query by claimant id per profiling
sreuland
added a commit
that referenced
this issue
May 25, 2022
* #4382: refined the placement of LIMIT clause on claimant balance query by claimant id per profiling results.
sreuland
added a commit
that referenced
this issue
May 26, 2022
* #4382: refined the placement of LIMIT clause on claimant balance query by claimant id per profiling results.
sreuland
added a commit
that referenced
this issue
Jun 9, 2022
* #4382: refined the placement of LIMIT clause on claimant balance query by claimant id per profiling results.
@jcx120 , with the incident document and the horizon 2.17.1/2.18.0 releases included optimizations based on findings, this ticket can likely be moved to done? |
Yes - updated to done. thanks |
sreuland
added a commit
to sreuland/go
that referenced
this issue
Aug 7, 2022
…IT depending on whether paging cursor parameters are present or not
sreuland
added a commit
to sreuland/go
that referenced
this issue
Aug 7, 2022
…ce query by claimant id per profiling
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tasks:
The text was updated successfully, but these errors were encountered: