You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2018. It is now read-only.
Currently, when the write manager creates a new instance queue, each queue is created with the same size, regardless of how many instances there are. However, this can lead to unbounded memory usage as the number of instances increases. Instead of being given a constant queue size upon configuration, the write manager should be given a total queue size target and should try to size the instance queues such that the total size of all the queues is less than the target total size.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, when the write manager creates a new instance queue, each queue is created with the same size, regardless of how many instances there are. However, this can lead to unbounded memory usage as the number of instances increases. Instead of being given a constant queue size upon configuration, the write manager should be given a total queue size target and should try to size the instance queues such that the total size of all the queues is less than the target total size.
The text was updated successfully, but these errors were encountered: