State of Clojure 2016 – Results and Analysis

Re:State of Clojure 2016 – Results and Analysis by pron on Tuesday February 07, 2017 @03:28PM (#13592443)

By default, the JVM will use all the memory you give it. Have you tried simply setting a small maximum heap size? You can use VisualVM to visualize the heap and GC. Deep monitoring is one of the JVM's greatest strengths.

[ Parent | on HN ]

Re:State of Clojure 2016 – Results and Analysis by hammerandtongs on Tuesday February 07, 2017 @03:51PM (#13592673)

Yes this was my thinking on how to proceed.

I'm just kind of surprised and disconcerted how little I could find on the web, specifically for minimizing footprint.

[ Parent | on HN ]

Re:State of Clojure 2016 – Results and Analysis by pron on Tuesday February 07, 2017 @04:02PM (#13592770)

The JVM does not lack in documentation and advice; Clojure is riding on that.

[ Parent | on HN ]