You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/07/27 05:41:24 UTC
[GitHub] [arrow-ballista] yahoNanJing opened a new issue, #101: Leverage Atomic for the in-memory states in Scheduler
yahoNanJing opened a new issue, #101:
URL: https://github.com/apache/arrow-ballista/issues/101
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) -->
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**
<!-- A clear and concise description of what you want to happen. -->
Therefore, we propose to introduce Atomic for the states to change the write lock to the read lock.
**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-ballista] andygrove closed issue #101: Leverage Atomic for the in-memory states in Scheduler
Posted by GitBox <gi...@apache.org>.
andygrove closed issue #101: Leverage Atomic for the in-memory states in Scheduler
URL: https://github.com/apache/arrow-ballista/issues/101
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org