You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we're building services that use the new HybridCache with a redis backend. One of the limitations is deserialization takes place for every get request, even for the IMemoryCache in process store. This is a design choice of the library and can be avoided by adding an attribute to the class.
I think it would be beneficial to have an immutable version of the different resource classes so that cache look ups are optimized and CPU overhead is reduced.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi, we're building services that use the new HybridCache with a redis backend. One of the limitations is deserialization takes place for every get request, even for the IMemoryCache in process store. This is a design choice of the library and can be avoided by adding an attribute to the class.
I think it would be beneficial to have an immutable version of the different resource classes so that cache look ups are optimized and CPU overhead is reduced.
All reactions