This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-27
Channels
- # announcements (1)
- # babashka (7)
- # beginners (60)
- # calva (24)
- # cider (2)
- # cljdoc (9)
- # clojure (21)
- # clojure-australia (1)
- # clojure-europe (2)
- # clojurescript (26)
- # core-async (89)
- # datalog (11)
- # datomic (40)
- # fulcro (24)
- # graalvm (5)
- # luminus (1)
- # meander (1)
- # numerical-computing (1)
- # off-topic (3)
- # shadow-cljs (6)
- # test-check (10)
- # tools-deps (7)
- # xtdb (18)
Is there a trick for finding the cause of the size of a native image? I'm already at 50mb!
@dominicm Yes, check if there is any code using require, resolve or find-var, etc in non-top-level code (i.e. function bodies)
A good strategy for this, I find, is adding code to your binary in small increments and checking the size at every step. Often I just copy the code from libraries and comment out function bodies until I find the source of the bloat
You can also maybe use this: https://github.com/lread/clj-graal-docs#report-what-is-being-analyzed I haven't used it as much, but the output may be useful