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
Store records in off-heap memory #528
Comments
Probably we should simply store the trx intent log in a Chronicle map instead of a simple |
https://minborgsjavapot.blogspot.com/2019/07/java-chroniclemap-part-1-go-off-heap.html Should'nt be hard to implement. |
Hey @JohannesLichtenberger Guten tag , would like to work on this can you please assign this to me. |
@abhin-dynamify I wonder if serialization of page (fragments) and deserialization will be an issue and if it's faster or even slower. Same for Caffeine caches (the lightweight buffer manager)... that said, with the Caffeine caches, if the maximum sizes are too large, I've had severe performance issues regarding the GC (especially with the ZGC, apparently maybe because it is not generational yet). |
We can try and compare performance in a separate branch 👍 |
@abhin-dynamify hope it makes sense. Do you work on this? |
yeah i am working on it |
@abhin-dynamify did you have time? |
In order to keep GC to a minimum (despite of low latency Garbage Collectors as for instance Shenandoah), we could try to store the records/nodes off-heap using the foreign memory API for instance, and compare performance.
The text was updated successfully, but these errors were encountered: