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

More suggestion folks use offheap block cache

This commit is contained in:
stack 2014-07-18 16:56:33 -07:00
parent 19979d770d
commit 60d3e3c905
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/main/docbkx/performance.xml
View File

@ -183,6 +183,8 @@
save a bit of YGC churn and allocate in the old gen directly. </para> save a bit of YGC churn and allocate in the old gen directly. </para>
<para>For more information about GC logs, see <xref <para>For more information about GC logs, see <xref
linkend="trouble.log.gc" />. </para> linkend="trouble.log.gc" />. </para>
<para>Consider also enabling the offheap Block Cache. This has been shown to mitigate
GC pause times. See <xref linkend="block.cache" /></para>
</section> </section>
</section> </section>
</section> </section>
@ -723,6 +725,8 @@ htable.close();
<methodname>setCacheBlocks</methodname> method. For input Scans to MapReduce jobs, this <methodname>setCacheBlocks</methodname> method. For input Scans to MapReduce jobs, this
should be <varname>false</varname>. For frequently accessed rows, it is advisable to use the should be <varname>false</varname>. For frequently accessed rows, it is advisable to use the
block cache.</para> block cache.</para>
<para>Cache more data by moving your Block Cache offheap. See <xref linkend="offheap.blockcache" /></para>
</section> </section>
<section <section
xml:id="perf.hbase.client.rowkeyonly"> xml:id="perf.hbase.client.rowkeyonly">