You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,3 +17,7 @@ It can be all too easy to allocate more memory by constructing more classes or s
17
17
#### Plan for the worst, but code for the best
18
18
19
19
Thread safety is important and in many cases should be assured. But when the 99% case is the local use of a class, over-engineering can simply create unnecessary overhead and contention.
20
+
21
+
#### Let the GC do its job
22
+
23
+
Aggressively attempting to help out the garbage collector can be serious anti-pattern as you are simply slowing down your own application in order to avoid GC operations which might actually be helping your performance in total by deferring cleanup.
0 commit comments