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

get_task_metrics() is expensive and must be destroyed #2360

Closed
divergentdave opened this issue Dec 14, 2023 · 2 comments · Fixed by #2686
Closed

get_task_metrics() is expensive and must be destroyed #2360

divergentdave opened this issue Dec 14, 2023 · 2 comments · Fixed by #2686

Comments

@divergentdave
Copy link
Collaborator

Here's a recently executed query plan:

image

@inahga
Copy link
Contributor

inahga commented Jan 23, 2024

From discussion out of band, we probably will want to delete this function as-it-is. While it has information that might be useful, it is slow for large tasks even with index scans, there may be better ways to get the same information, and it isn't currently useful for billing purposes.

@tgeoghegan
Copy link
Contributor

tgeoghegan commented Jan 30, 2024

Elsewhere we have work underway (#2293, #2508, #2537, #2553, #2513) to introduce a superior task metrics solution. So I think this issue only tracks deleting the old solution once the new one is deployed.

@inahga: besides deploying the new stuff, are there other blockers to deleting the old stuff?

@tgeoghegan tgeoghegan changed the title get_task_metrics() is expensive get_task_metrics() is expensive and must be destroyed Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants