#deno repl start time in container

1 messages · Page 1 of 1 (latest)

stable schooner
#

Why does deno repl take a couple seconds to start in a container the second time around, and starts nearly instantaneously the second time around in the host system? It's on OS X with colima (deno is running on x86) FWIW.

#

I use bash to go to my container. using docker stat I can tell it gives up its memory use right away when I exit, which is desired behavior, I just wonder if I could tell it to cache it. Also I wonder if it's caching it in memory on mac.

#

I might have figured most of it out if it's the disk cache.