This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-16
Channels
- # announcements (7)
- # babashka (1)
- # beginners (25)
- # calva (7)
- # cider (15)
- # clj-kondo (13)
- # cljdoc (14)
- # clojure (151)
- # clojure-europe (4)
- # clojure-hamburg (2)
- # clojure-italy (22)
- # clojure-nl (57)
- # clojure-spec (12)
- # clojure-uk (6)
- # clojuredesign-podcast (5)
- # clojurescript (12)
- # core-async (8)
- # cursive (26)
- # datascript (9)
- # datomic (92)
- # emacs (4)
- # fulcro (7)
- # graalvm (1)
- # graphql (2)
- # instaparse (3)
- # jobs (1)
- # jvm (2)
- # kaocha (6)
- # nrepl (3)
- # off-topic (5)
- # re-frame (45)
- # reagent (5)
- # reitit (18)
- # ring (1)
- # shadow-cljs (89)
- # slack-help (9)
- # spacemacs (2)
- # sql (54)
- # tools-deps (75)
- # vim (28)
- # xtdb (17)
- # yada (31)
Hello! I was looking at the logs of a web server when I found:
OpenJDK 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
After looking at the set of JVM options we use when running java (openjdk 8) I found:
-server
-Xms5G
-Xmx5G
-XX:+DoEscapeAnalysis
-XX:+UseParNewGC
-XX:+UseConcMarkSweepGC
-XX:+CMSConcurrentMTEnabled
-XX:+CMSIncrementalMode
-XX:MaxNewSize=257m
-XX:NewSize=256m
-XX:+UseTLAB
-XX:MaxTenuringThreshold=0
I'm not going to update java right now, but I'd like to know if it is safe to remove this +CMSIncrementalMode
flag? And if it is actually doing something?From a couple of articles it seems java is dropping support for the Concurrent Mark Sweep Garbage Collector, they will focus on G1. Since latest Clojure still supports java 8 I'm not tweaking those settings yet. - Why CMS Garbage Collector deprecating: https://www.linkedin.com/pulse/jvm-why-cms-garbage-collector-deprecating-kunal-saxena/ - Info about different garbage collectors: https://www.baeldung.com/jvm-garbage-collectors