This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-12
Channels
- # adventofcode (2)
- # aleph (2)
- # announcements (5)
- # aws (5)
- # babashka (25)
- # beginners (167)
- # calva (8)
- # cider (1)
- # clj-kondo (3)
- # cljsrn (19)
- # clojure (87)
- # clojure-conj (7)
- # clojure-dev (19)
- # clojure-europe (1)
- # clojure-italy (14)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-norway (3)
- # clojure-spec (18)
- # clojure-uk (29)
- # clojuredesign-podcast (3)
- # clojurescript (40)
- # clojurex (11)
- # core-async (13)
- # core-logic (2)
- # cursive (16)
- # data-science (4)
- # datascript (10)
- # datomic (53)
- # emacs (1)
- # events (15)
- # fulcro (71)
- # jobs (1)
- # jvm (2)
- # malli (4)
- # nrepl (2)
- # pathom (74)
- # re-frame (1)
- # reitit (19)
- # remote-jobs (1)
- # rewrite-clj (18)
- # ring (2)
- # shadow-cljs (132)
- # spacemacs (22)
- # tools-deps (65)
Hey, maybe not the best place to ask but trying to understand what’s the right size to use for the heap of an application. I see different opinions online with people saying that the max heap size should be 25% of your available memory and others arguing it should be ~80% Anybody with experience and insights in how to tune this properly ?
@thomas.ormezzano based on my experience, for the applications that me and my team are running was to set a min and max heap to a concrete value (e.g. 2G or 125M) - it's a bit of a trial and error but we found that this way we know if we can move applications to smaller/bigger machines rather than let them just consume available RAM (if set to 80%) or underutilize resources (if set to 25%)