high memory usage using compiled binary in docker
I'm fairly new to docker. I tried something similar to what's in the docs here, with deno task build in the build stage, before trying to run the compiled version of my app.
Memory usage is very high (800mb) in both versions. Running the compiled version of the app on my machine only uses around 70mb.
How can I decrease the memory usage of the docker container? I'd love to get it under 200mb.
Any help would be greatly appreciated!
link to my repo for context if that helps:
https://github.com/candirugame/candiru
9 Replies
From what I've seen, Deno version 2 and up has a higher start up memory cost when run in Docker. I've seen similar numbers to what you're describing. They have eventually dropped a bit but the baseline is still several hundred mb higher than prior to Deno v2.0.0
I’ve noticed that setting the memory limit around 800 drops it to around 500, which is still much higher than I’d like
Setting it below 800 causes a crash :/
They have eventually dropped a bitHave links for that? I'm interested in containerized performance. That almost sounds like a bug. (ex: JVMs used to use the OS memory, not the container memory, to allocate initial heap.) @hob how big is that dist/ that you include? I wonder if it's getting loaded into memory at startup?
/dist is around 12.5MB. I don't actually need that at all in the runtime stage though. Does it still have access to this at runtime?
Yes,
deno compile --include includes the file contents into the compiled file so that they're available at runtime without having to read them from disk.The compiled exe is roughly 700mb.. wondering if the entire thing gets pulled into memory?
700mb? And your dist/ was only 12MB? So you just have a LOT of dependencies?
Running the compiled version of the app on my machine only uses around 70mb.Is that binary also 682 MB? If not, it seems your build processes have diverged.
Maybe.. does this seem excessive?
deno.json
package.json
I can try building on Linux x86 rather than MacOS arm. Will report back
I just mean, you said you can compile it and run it outside of docker and it only takes 70mb. that's 1/10th the size. I wonder if you're compiling a very different set of dependencies. (and that --include dist/ looks like a likely cuplrit.)
If you can compare the compiled binary size between the two different binaries that are showing the different memory usage, that might confirm that that's the issue.