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

Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/12/02 21:25:12 UTC

[jira] [Created] (HBASE-12615) Document GC conserving guidelines for contributors

Andrew Purtell created HBASE-12615:
--------------------------------------

             Summary: 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
(v6.3.4#6332)