hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12615) Document GC conserving guidelines for contributors
Date Tue, 02 Dec 2014 21:07:13 GMT

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

Lars Hofhansl commented on HBASE-12615:

big +1. Ran into and fixed at least one of each of the categories (except for the Regex stuff),
didn't think to document that. That's a great idea.

> Document GC conserving guidelines for contributors
> --------------------------------------------------
>                 Key: HBASE-12615
>                 URL: https://issues.apache.org/jira/browse/HBASE-12615
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Andrew Purtell
> LinkedIn put up a blog post with a nice concise list of GC conserving techniques we should
document for contributors. Additionally, when we're at a point our build supports custom error-prone
plugins, we can develop warnings for some of them. 
> Source: http://engineering.linkedin.com/performance/linkedin-feed-faster-less-jvm-garbage
> - Be careful with Iterators
> - Estimate the size of a collection when initializing
> - Defer expression evaluation
> - Compile the regex patterns in advance
> - Cache it if you can
> - String Interns are useful but dangerous
> All good advice and practice that I know we aim for. 

This message was sent by Atlassian JIRA

View raw message