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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2014/05/22 02:19:39 UTC

[jira] [Resolved] (HBASE-4812) GC benchmarking and analysis tools

     [ https://issues.apache.org/jira/browse/HBASE-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-4812.
--------------------------

    Resolution: Later

Resolving as later and superceded by HBASE-9806 and its ilk.

> GC benchmarking and analysis tools
> ----------------------------------
>
>                 Key: HBASE-4812
>                 URL: https://issues.apache.org/jira/browse/HBASE-4812
>             Project: HBase
>          Issue Type: Task
>          Components: io
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Minor
>         Attachments: GCBench.patch
>
>
> One of the challenges of debugging GC issues is that it can take a long time to reproduce GC pauses.  Isolating the LRU block cache and benchmarking it independently can more easily cause measurable and reproducible GC issues.
> In addition, making sense of the noisy GC logs is difficult.
> This may not be for commit, but I wanted to share some code and scripts I've written to tackle these problems.



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