Hi! Can anyone give me some tips on how to reduce the size of the binary file? I'm compiling a simple CLI Clojure project that only depends on cheshire and clj-http-lite. The size of the file is 45-46Mb.

which is tolerantly, but still worths to be reduced

I've tried to replace clj-http-lite with a primitive Clojure wrapper on top of http://java.net.http.HttpClient, but the size didn't change

nor when I swap cheshire with clojure.data.json

@igrishaev you can get this down to probably 15 mb. usually this inflation occurs when you're dynamically requiring vars somewhere

so it kind of depends on your coding style

if your code is public then I could try to pin it down

having said this, babashka also contains cheshire and is compatible with clj-http-lite (but also has other http clients on board) so you can maybe also run it with that already, depending on your use case

@igrishaev as the author of etaoin, you might also be interested in seeing what I did to make it run with babashka: https://github.com/babashka/pod-babashka-etaoin

thanks, @borkdude! The code is not public yet, I need to check if I can share it

actually, I don't require any vars, but read a resource file in runtime

@igrishaev thanks for inviting me to the repo. I see your'e using clojure.pprint and that uses vars dynamically.

this is likely the culprit of the image size bloat. try without pprint for now. I know a workaround for this

@igrishaev See https://clojure.atlassian.net/browse/CLJ-2582

Yes I saw this ticket, and also had some compilation errors with clojure < 1.10.2

yes, see topic of this channel. just use the newest clojure

wow, without pprint, the size is 28M

I hope the patch will make it into Clojure, that will make clojure.pprint better to use with graalvm

which is something close to golang

You can fix this in user space though with alter-var-root

The smallest image I can get is around 10mb or so

with Clojure that is

I wonder if it's possible to reduce the size even more

@igrishaev I found that when using httpkit as the client, this is only takes 1.5mb or so

even including the webserver :)

oh, that's good to know. Will try it

also, is it ok to embed resources into the binary file?

I have a huge JSON file. There is an option to generate a static namespace file before compilation

say, to produce a .clj file with one var (def my-data ...) from that json

yes, that is ok

you can also read the JSON from the resource in the image though

then you have to configure it to include that resource

yes, I did it

I just thought that maybe it brings some runtime shananigence

but if you have the compiled namespace in the image then you don't need to include the JSON anymore right

What I mean: you can make (slurp`(io/resource "my-json.json")` )work at runtime in the image

but this requires extra config

right, I have this in my command: -H:IncludeResources='.*my-file.json$' \

yeah, but if you do the processing of this json at compile time (a top level def) then you don't need this

yep, that also be faster on startup