Fork me on GitHub
#graalvm
<
2022-03-04
>
souenzzo12:03:04

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.

souenzzo14:03:56

tnks. at first look, i thought that is was just about heap size

souenzzo14:03:11

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?

souenzzo14:03:50

Oh. binary size = core + heap. OK!

borkdude13:03:10

@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.

souenzzo14:03:24

I'm generating reflect-config.json dynamically with an empty filter.json a better filter will result in smaller binaries?

souenzzo14:03:20

do you include core.async in bb?

souenzzo14:03:34

Do you have the DashboardDump files for bb in somewhere? I would like to compare with my dump.

borkdude14:03:34

I don't but you can of course create it yourself. There is a script/uberjar and a script/compile in the babashka repo. In script/compile you can add this option.

👌 1