tag:blogger.com,1999:blog-3946011063058389308.post8536528197967331117..comments2009-10-31T01:53:36.795-07:00Grid Dynamicshttp://www.blogger.com/profile/18125799569183836823noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3946011063058389308.post-36774293031389015062009-10-31T01:53:36.795-07:002009-10-31T01:53:36.795-07:00Hi Cameron,<br /><br />I have missed &lt;partitioned&gt; option among 3.5 features. It is very interesting. Storing keys in heap is a serious limitation for large scale off-heap storage.<br />I tried this option, but results were unexpected.<br />I think it is better to discuss them on Coherence forum, please see my <a href="http://forums.oracle.com/forums/thread.jspa?threadID=980163&amp;tstart=0" rel="nofollow">post</a>.<br /><br />Anyway I&#39;m going to continue measuring different storage schemes and post report. Looks like things like eviction also have great impact on heap consumption and I cannot ignore them.<br /><br />Regards,<br />AlexeyAlexey Ragozinhttp://www.blogger.com/profile/13720493857045012756noreply@blogger.comtag:blogger.com,1999:blog-3946011063058389308.post-56056844031839940262009-10-29T12:55:37.211-07:002009-10-29T12:55:37.211-07:00Nice article. :-)<br /><br />If you use the &quot;partitioned&quot; option, then the separate index of keys per partition is delegated to the PartitionAwareBackingMap. That means with off-heap, it shouldn&#39;t use any heap memory for the key index.<br /><br />Peace,<br /><br />Cameron Purdy | Oracle CoherenceCameronhttp://www.blogger.com/profile/06987724607105300730noreply@blogger.com