|
Loading...
|
nhusers@googlegroups.com
[Prev] Thread [Next] | [Prev] Date [Next]
[nhusers] Re: Should I use NH cache for large collections? Jason Meckley Wed Sep 28 19:00:58 2011
1. yes, but only to the degree of how it configured. syscache, syscache2, memcached all have different configuration and are designed for a specific type of cache. pick the one that works best for you. 2. not if you are going to implement 2nd level caching. 3. this question is irrelevant. the "size" of an entity will have more of an impact on effective query plans, concurrency and consistency. there is another view point. if this is relatively static data that you just want to throw into cache, why not use a persistent hashtable or some other "nosql" data store. this may be more effective than1. using a relational database for non-relational data and 2. storing everything in memory. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/4nCcK63wuRoJ. 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.
- [nhusers] Should I use NH cache for large collections? mynkow 2011/09/28
- [nhusers] Re: Should I use NH cache for large collections? Jason Meckley 2011/09/28 <=
- [nhusers] Re: Should I use NH cache for large collections? fel0niousmonk 2011/09/30