Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

edit on why bucketcache

This commit is contained in:
stack 2014-08-08 11:22:47 -07:00
parent ef70ce8b50
commit 1f1a676cfe
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/main/docbkx/book.xml
View File

@ -2113,9 +2113,11 @@ rs.close();
</para> </para>
<para>Fetching will always be slower when fetching from BucketCache, <para>Fetching will always be slower when fetching from BucketCache,
as compared with the native onheap LruBlockCache. However, latencies tend to be as compared to the native onheap LruBlockCache. However, latencies tend to be
less erratic across time, because there is less garbage collection. This is why less erratic across time, because there is less garbage collection when you use
you'd use BucketCache, so your latencies are less erratic and to mitigate GCs BucketCache since it is managing BlockCache allocations, not the GC. If the
BucketCache is deployed in offheap mode, this memory is not managed by the
GC at all. This is why you'd use BucketCache, so your latencies are less erratic and to mitigate GCs
and heap fragmentation. See Nick Dimiduk's <link and heap fragmentation. See Nick Dimiduk's <link
xlink:href="http://www.n10k.com/blog/blockcache-101/">BlockCache 101</link> for xlink:href="http://www.n10k.com/blog/blockcache-101/">BlockCache 101</link> for
comparisons running onheap vs offheap tests. Also see comparisons running onheap vs offheap tests. Also see