DanP
Reputation: 6478
Why does the StackExchangeRedis NHibernate Second Level Cache require a locking mechanism?
This provider has a locking mechanism, but other related providers (most notably NHibernate.Caches.CoreDistributedCache.Redis) have no such mechanism.
Is there a specific use case of this provider that requires this?
I'm ideally looking to make use of Redis as a 2LC for NHibernate, but the locking support in this provider has serious performance implications for our application, so I'm wondering if I can simply override this behavior to make it a no-op if it's not important for our usage of it.
Upvotes: 2
Views: 97
Answers (0)
Related Questions
- What are the First and Second Level caches in (N)Hibernate?
- Removing objects from NHibernate second level cache
- Third-Level cache for NHibernate
- Should NHibernate clear distributed 2nd Level Cache on ISessionFactory.Dispose?
- NHibernate: second level cache expiration
- nHibernate second-level cache with memcached and random invalid casts
- How to clear the entire second level cache in NHibernate
- Second level cache does not cache filtered collections in NHibernate?
- Nhibernate and SetCacheable with second level cache
- NHibernate - counters with concurrency and second-level-caching