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

Leverage Atomic for the in-memory states in Scheduler #101

Closed
yahoNanJing opened this issue Jul 27, 2022 · 0 comments · Fixed by synnada-ai/arrow-ballista#2 or #319
Closed

Leverage Atomic for the in-memory states in Scheduler #101

yahoNanJing opened this issue Jul 27, 2022 · 0 comments · Fixed by synnada-ai/arrow-ballista#2 or #319
Labels
enhancement New feature or request

Comments

@yahoNanJing
Copy link
Contributor

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Currently we leverage read write lock for the in-memory states in scheduler in global level, which is too coarse. When tens of thousands of states need to be updated, it will downgrade the whole system performance because of the write lock.

Describe the solution you'd like

Therefore, we propose to introduce Atomic for the states to change the write lock to the read lock.

Describe alternatives you've considered

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant