-
Notifications
You must be signed in to change notification settings - Fork 401
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
ExpandableDirectByteBuffer maximum capacity only 1GB #272
Comments
This would require changing all of the accessor methods that take in a index value and switch it from a int to a long. This in turn would break compatibility with the array backed implementations of the DirectBuffer. |
What do you think, are there other pitfalls besides compatibility that prevent the increase in the maximum size? Only this limitation does not allow using Aeron in our project, where the buffer size must be at least 60 gigabytes. |
ByteBuffer and byte arrays cannot be larger be larger than int capacity. |
That is, if Argon would like to support a ring buffer of this size, then the only option is to work with files directly (memory-mapped files, dev/shm, etc.)? |
Mapped files in Java still return a |
First of all as pointed out @mjpt777 the underlying size cannot exceed If you need more than 2GB of storage you can use |
maximum capacity of ExpandableDirectByteBuffer is only 1GB
I think the reason is that the type of index is int
Do you think it's better to change int to long and expand the capacity?
The text was updated successfully, but these errors were encountered: