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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
