-
Notifications
You must be signed in to change notification settings - Fork 578
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
Add multi-level cache design #375
Comments
actually we keep values in the heap. Could you elaborate? |
I have a scenario where I want to store 10,000,000 key-value in the local cache, but this value is a relatively complex object. According to the current logic of bigcache, the value will be serialized into bytes for storage, and then actually, when I want to use Sometimes, I need to deserialize value from bytes into objects. Since this service is a high-frequency request, value will be serialized into objects repeatedly, causing a lot of CPU consumption. So I wonder if I can add a cache and store high-frequency key-values directly in the map (for example, using segmentation locks). This can reduce the cost of deserializing values from bytes into objects. |
Like ehcache,Some hotspot key-values reside directly in the heap, while other key-values are stored in the original way.
The text was updated successfully, but these errors were encountered: