Hi, After I tried to use cache with Velocity, it seems that tuyrning on cache gives poor performance. After digging down, I found that UpdateTimestampCache has a lot of cache miss because Hibernate/ NHibernate check if timestamp doesn't exist in cache, then it means cache is up to date. This, however, in the distributed cache scenario, has pretty high cost. Instead of checking just local cache, it has to go through remote caches to check the item. Does it make sense to put an item in the cache to avoid cache miss issue instead of not putting timestamp at all?
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
