[
https://issues.apache.org/jira/browse/HBASE-12615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946275#comment-14946275
]
Hudson commented on HBASE-12615:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #6880 (See
[https://builds.apache.org/job/HBase-TRUNK/6880/])
HBASE-12615 Document GC conserving guidelines for contributors (mstanleyjones:
rev d55f4aee4ff7e952eedbd04565e1b5f7b67379f5)
* src/main/asciidoc/_chapters/developer.adoc
> 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
> Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-12615.patch
>
>
> 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)
