Bigmemory serializes java objects then stores the serialized form in DirectByteBuffers, which isn't quite exactly what we want...
Needless to say a number of us have been poking at the DBB and Unsafe APIs and have a few ideas :-) On Thu, Jan 20, 2011 at 10:39 AM, Todd Lipcon <[email protected]> wrote: > On Thu, Jan 20, 2011 at 10:34 AM, Vladimir Rodionov <[email protected] >> wrote: > >> BigMemory anyone? >> >> http://www.terracotta.org/bigmemory >> >> > Yea, something like that, minus the commercial license ;-) > > -Todd > ____ > >> From: Todd Lipcon [[email protected]] >> Sent: Thursday, January 20, 2011 9:33 AM >> To: dev >> Subject: Heap fragmentation >> >> I did some experiments to understand our full GC issues better last night. >> Here are the results: >> http://people.apache.org/~todd/hbase-fragmentation/ >> >> <http://people.apache.org/~todd/hbase-fragmentation/>Basically my >> conclusion >> here is that (for these YCSB workloads) the memstore is way worse for heap >> fragmentation than the block cache. >> >> Also we now have some tools and reference for comparison if we make any >> changes to memstore to try to combat this issue. >> >> -Todd >> -- >> Todd Lipcon >> Software Engineer, Cloudera >> > > > > -- > Todd Lipcon > Software Engineer, Cloudera >
