Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker container uses massive amount of memory to boot (150MB) #27624

Open
danthegoodman1 opened this issue Jan 10, 2025 · 1 comment
Open

Docker container uses massive amount of memory to boot (150MB) #27624

danthegoodman1 opened this issue Jan 10, 2025 · 1 comment
Labels
needs investigation requires further investigation before determining if it is an issue or not

Comments

@danthegoodman1
Copy link

danthegoodman1 commented Jan 10, 2025

docker run -it --rm denoland/deno:2.1.5 repl

150MB from docker container stats:
image

For reference, I observed the following for other container images:

  • docker run -it --rm python:3.12 python: 11MB
  • docker run -it --rm node:22 node: 11MB
@bartlomieju bartlomieju added the needs investigation requires further investigation before determining if it is an issue or not label Jan 20, 2025
@nathanwhit
Copy link
Member

The primary source of memory usage is the typescript compiler, which deno runs to provide auto completions for the REPL. This is the same way that deno's LSP provides completions to editors. I'm not sure about python, but node dynamically searches prototypes at runtime to provide completions (which is much less intensive than running TSC for type information).

The more fair comparison would be how much memory it takes to run an empty file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs investigation requires further investigation before determining if it is an issue or not
Projects
None yet
Development

No branches or pull requests

3 participants