-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[FEATURE]: Storing values larger than 2 GB #2040
Labels
kind/feature
Something completely new we should consider.
Comments
I have the same problem, 2G is too little for me, we need more than 8G |
Same here |
This issue has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open. |
Still relevant. |
This issue has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open. |
Still relevant. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you tried Badger before this proposal? and did not find anything similar?
None
What you wanted to do.
I wanted to set
ValueLogFileSize
to 6 GB.What you actually did.
Called
opts.WithValueLogFileSize(6 * 1024 * 1024 * 1024)
.Why wasn't it great, with examples.
I got error
Invalid ValueLogFileSize, must be in range [1MB, 2GB)
.Additional information.
Could this limit be lifted on 64bit systems? It seems to me that this is just to support mmap on 32 bit systems and there is really no design limitation why not to support larger values? On my system, I have:
So a bit less than 2^47 (128 TiB) could be the max limit for mmap on my system.
The text was updated successfully, but these errors were encountered: