Re:135M messages a second between processes in Java (2013)
by mindcrime on Sunday August 14, 2016 @01:31AM
(#12284387)
It's not really that bad. And on the plus side, VisualVM helps a ton because you can connect to a running JVM and actually see what's happening with the garbage collector (among other things).
[ Parent
| on HN ]
Re:135M messages a second between processes in Java (2013)
by rb2k_ on Tuesday August 16, 2016 @06:28PM
(#12301118)
I've seen high throughput apps doing 45 second "stop the world" garbage collection cycles because of high disk I/O and enabled GC logging (the process just sat there waiting for some I/O time to flush the GC log file).
So in theory tuning GC isn't thaaaaaat complicated. In practice however I've seen horrible things :(
Re:135M messages a second between processes in Java (2013)
by mindcrime on Tuesday August 16, 2016 @07:12PM
(#12301362)
Sure, I'm not saying pathological cases can't come up. Just that JVM GC tuning isn't usually that big a deal. IOW, it isn't some "black art" that only uber-wizards can comprehend..