Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Linux
-
Docs
Description
Currently SerializingCache is partially off heap, keys are still stored in JVM heap as BB,
- There is a higher GC costs for a reasonably big cache.
- Some users have used the row cache efficiently in production for better results, but this requires careful tunning.
- Overhead in Memory for the cache entries are relatively high.
So the proposal for this ticket is to move the LRU cache logic completely off heap and use JNI to interact with cache. We might want to ensure that the new implementation match the existing API's (ICache), and the implementation needs to have safe memory access, low overhead in memory and less memcpy's (As much as possible).
We might also want to make this cache configurable.
Attachments
Attachments
Issue Links
- links to