You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Manukranth Kolloju (JIRA)" <ji...@apache.org> on 2014/06/27 02:30:26 UTC

[jira] [Commented] (HBASE-11417) Determining and storing the Write/Read Amplification inside HBase

    [ https://issues.apache.org/jira/browse/HBASE-11417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045382#comment-14045382 ] 

Manukranth Kolloju commented on HBASE-11417:
--------------------------------------------

Was there any work done in this direction already ?

> Determining and storing the Write/Read Amplification inside HBase
> -----------------------------------------------------------------
>
>                 Key: HBASE-11417
>                 URL: https://issues.apache.org/jira/browse/HBASE-11417
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Manukranth Kolloju
>            Assignee: Manukranth Kolloju
>
> We should be able to calculate the read and write amplification from inside hbase and store it in the StoreFiles. This should give us a broad picture of the usage pattern to identify and answer some key questions
> * What is the read/write amplification.
> * What portion of the data can be served out of Cache/Flash or Disk and how do we identify it.
> * Whether HBase is the best fit for the work load.
> * Or whether HBase was a right fit for the work load in the first place.
> etc.



--
This message was sent by Atlassian JIRA
(v6.2#6252)