[
https://issues.apache.org/jira/browse/HBASE-5349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204087#comment-13204087
]
Jean-Daniel Cryans commented on HBASE-5349:
-------------------------------------------
Good question, I don't think looking at requests is good enough... instead we
could look at how both are used and if there's adjustment to be made. For
example, if you have a read heavy workload then the memstores would not see a
lot of usage... same with write heavy, the block cache would be close to empty.
Those two are clear cuts, now for those workloads in between it gets a bit
harder. Maybe at first we shouldn't even try to optimize them.
I think it should also be done incrementally, move like 3-5% of the heap from
one place to the other every few minutes until it settles.
> Automagically tweak global memstore and block cache sizes based on workload
> ---------------------------------------------------------------------------
>
> Key: HBASE-5349
> URL: https://issues.apache.org/jira/browse/HBASE-5349
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.92.0
> Reporter: Jean-Daniel Cryans
> Fix For: 0.94.0
>
>
> Hypertable does a neat thing where it changes the size given to the CellCache
> (our MemStores) and Block Cache based on the workload. If you need an image,
> scroll down at the bottom of this link:
> http://www.hypertable.com/documentation/architecture/
> That'd be one less thing to configure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
