This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-04
Channels
- # announcements (19)
- # babashka (11)
- # babashka-sci-dev (9)
- # beginners (71)
- # calva (25)
- # cider (1)
- # clara (36)
- # clj-kondo (47)
- # clojure (65)
- # clojure-dev (64)
- # clojure-europe (9)
- # clojure-nl (2)
- # clojure-seattle (1)
- # clojure-uk (2)
- # clojured (8)
- # clojurescript (17)
- # cursive (9)
- # data-science (36)
- # datahike (11)
- # emacs (10)
- # figwheel-main (19)
- # fulcro (15)
- # graalvm (12)
- # humbleui (5)
- # introduce-yourself (3)
- # jobs (10)
- # leiningen (4)
- # lsp (24)
- # malli (7)
- # nextjournal (23)
- # off-topic (1)
- # pedestal (2)
- # polylith (6)
- # portal (1)
- # re-frame (3)
- # reitit (2)
- # releases (2)
- # remote-jobs (1)
- # reveal (9)
- # shadow-cljs (13)
- # spacemacs (6)
- # xtdb (3)
There is tools to debug why my native-image is so big? I'm currently with ~90Mb. The code is just a "hello world" route in a http server.
https://github.com/clj-easy/graal-docs#visualize-what-is-in-your-native-image this could be useful
My current binary has 80Mb on disk
In the dashboard, it seems to have just 30Mb (10Mb of clojure + 5Mb of *java + 5Mb of *sun + ~10Mb of )
Is it expected? there is an "upfront" cost?
@souenzzo babashka has an http-server (http-kit) + a lot more libraries and is "only" 75mb. It really matters what you bring in and what kind of Clojure code is used. Dynamic requires/resolves can cause bloat.
I'm generating reflect-config.json
dynamically with an empty filter.json
a better filter will result in smaller binaries?