Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
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.