[
https://issues.apache.org/jira/browse/HBASE-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-11331:
---------------------------------
Attachment: HBASE-11331.03.patch
Parking an updated patch. Rebased onto master, adds a bit of instrumentation to
LruBlockCache when TRACE debugging is enabled, and adds an e2e test comparing
directly the flag enabled and disabled. The only testing I've done with this
one is {{mvn test -Dtest=org.apache.hadoop.hbase.io.hfile.*}}
I've not been able to reproduce the jagged blockcache size spikes in recent
runs. I'll take this patch through the ringer with my rig tomorrow, and report
back with my findings.
> [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-11331LazyBlockDecompressperfcompare.pdf, lazy-decompress.02.0.pdf,
> lazy-decompress.02.1.json, lazy-decompress.02.1.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)
