[
https://issues.apache.org/jira/browse/HBASE-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106147#comment-14106147
]
stack commented on HBASE-11331:
-------------------------------
You figure the compressor issue, our not reusing them?
13x the GC because we are doing 10x the throughput is fair enough. All other
numbers are very nice.
This is best case (when =false, we are seeking? Or is it always inside fscache?)
What is the 'cost' keeping stuff compressed? What if you do a run where all
fits in cache, for both cases?
> [blockcache] lazy block decompression
> -------------------------------------
>
> Key: HBASE-11331
> URL: https://issues.apache.org/jira/browse/HBASE-11331
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Attachments: HBASE-11331.00.patch, HBASE-11331.01.patch,
> HBASE-11331.02.patch, HBASE-11331.03.patch, HBASE-11331.04.patch,
> HBASE-11331.05.patch, HBASE-11331LazyBlockDecompressperfcompare.pdf,
> lazy-decompress.02.0.pdf, lazy-decompress.02.1.json,
> lazy-decompress.02.1.pdf, v03-20g-045g-false.pdf, v03-20g-045g-true-16h.pdf,
> v03-20g-045g-true.pdf
>
>
> Maintaining data in its compressed form in the block cache will greatly
> increase our effective blockcache size and should show a meaning improvement
> in cache hit rates in well designed applications. The idea here is to lazily
> decompress/decrypt blocks when they're consumed, rather than as soon as
> they're pulled off of disk.
> This is related to but less invasive than HBASE-8894.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
