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

Implement unwind information reset #45

Merged
merged 1 commit into from
May 28, 2024

Conversation

javierhonduco
Copy link
Owner

This implmementation has several shortcomings, and doesn't have any rate-limiting in place. We will continue to improve this and have plans to revisit how we store chunks (as this can be optimized) as well as how the unwind information is laid out to try to prevent expensive state resets.

Test Plan

Ran on busy hosts that used all shards. The state was resest and profiling continued as usual.

This implmementation has several shortcomings, and doesn't have any
rate-limiting in place. We will continue to improve this and have plans
to revisit how we store chunks (as this can be optimized) as well as how
the unwind information is laid out to try to prevent expensive state
resets.

Test Plan
=========

Ran on busy hosts that used all shards. The state was resest and
profiling continued as usual.
@javierhonduco
Copy link
Owner Author

cc @gmarler as this should fix the bug you reported. Let me know if that's not the case!

@javierhonduco javierhonduco merged commit 689a9e0 into main May 28, 2024
8 checks passed
@javierhonduco javierhonduco deleted the implement-unwind-info-reset branch May 28, 2024 18:24
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 this pull request may close these issues.

1 participant