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

The interruption and artifact APIs can do with some performance improvements #4871

Closed
droyad opened this issue Sep 6, 2018 · 5 comments

Comments

@droyad
Copy link
Contributor

commented Sep 6, 2018

These two APIs have bubbled to the top now that we have tackled most of the other API perf problems. The query is expensive and is called often from the Tasks page. It isn't cached and uses a LIKE on a RelatedDocumentIds table

@droyad droyad self-assigned this Sep 6, 2018
@droyad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 10, 2018

Just going to add an ETag for now, fixing up the query is non-trivial and would only lead to a marginal perf improvement.

@droyad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 10, 2018

1 similar comment
@droyad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 10, 2018

@droyad droyad closed this Oct 23, 2018
@octoreleasebot octoreleasebot added this to the 2018.8.13 milestone Oct 23, 2018
@octoreleasebot

This comment has been minimized.

Copy link

commented Oct 23, 2018

Release Note: The interruption and artifact APIs now have an ETag, lessening the load on the database

@MJRichardson MJRichardson modified the milestones: 2018.8.13, 2018.9.0 Oct 23, 2018
@lock

This comment has been minimized.

Copy link

commented Jan 21, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants
You can’t perform that action at this time.