If I have a `jvm heapSize=2048` value in server json that va cfml #box-products

If I have a `jvm.heapSize=2048` value in server.js...

seandaniels

05/31/2023, 1:10 PM

If I have a

jvm.heapSize=2048

value in server.json, that value is obviously used for the server when it starts. Is that value also used by Commandbox for other commands? For example, if I run

box install

will the Commandbox process also grab another 2GB of memory? I ask because I am running a server on an EC2 instance with 4GB memory and 2048 heapsize. Sometimes when I do a deploy the entire instance crashes when it gets to the

box install

part of the deploy (like can't even ssh to it). Trying to figure out why...

bdw429s

05/31/2023, 4:04 PM

@seandaniels Server settings have no affect on what the CLI does

bdw429s

05/31/2023, 4:05 PM

The CLI actually doesn't set a max heap so it's just going to grab whatever Java think it wants to ask the OS for.

bdw429s

05/31/2023, 4:05 PM

Normally, just running a one-off command will only take a few hundred megs, but I've also ran heavy duty task runners from the CLI and had it gobble up a couple Gigs of RAM

bdw429s

05/31/2023, 4:06 PM

If you want to prevent the CLI from taking over a certain amount, there are a couple ways to provide JVM args to the underlying Java process, but it depends on your OS

bdw429s

05/31/2023, 4:06 PM

https://commandbox.ortusbooks.com/usage/execution#a-d-hoc-jvm-args-for-the-cli

bdw429s

05/31/2023, 4:07 PM

You can set this on your server to keep the CLI from going over your set amount.

bdw429s

05/31/2023, 4:07 PM

Java can be a little greedy when you don't give it a max, so setting a max should still work just fine, it will just force Java to perform garbage collection a little more often 🙂

seandaniels

05/31/2023, 5:09 PM

Will give that a try, thanks!

seandaniels

05/31/2023, 5:10 PM

Like I said, it's just a

box install

so it didn't seem to me to be too heavy a task (probably a dozen or so packages?) but hey who knows. It was definitely happening repeatedly at that exact step in the deploy.

bdw429s

05/31/2023, 5:12 PM

Honestly, it may depend on how big the zip are you're downloading.

bdw429s

05/31/2023, 5:12 PM

If you're downloading hundreds of megs of stuff, that can create a good deal of memory churn

bdw429s

05/31/2023, 5:12 PM

And Java seems that it will always just ask the OS for more rather than bother running GC, lol

seandaniels

05/31/2023, 5:13 PM

Ah. Interesting. Yeah some of my packages might be pretty big. In particular, a "commons" library my apps use.

seandaniels

05/31/2023, 5:18 PM

Just verifying, if I'm using

commandbox-dotenv

and I'm on *nix and I add

BOX_JAVA_ARGS="-Xms512m -Xmx512m"

to my .env, that should do it, eh?

bdw429s

05/31/2023, 5:18 PM

seandaniels

05/31/2023, 5:18 PM

heh

seandaniels

05/31/2023, 5:18 PM

glad I asked

bdw429s

05/31/2023, 5:19 PM

the dot env module has nothing at all to do with the bootstrapping of CommandBox itself!

seandaniels

05/31/2023, 5:19 PM

Right, ok

bdw429s

05/31/2023, 5:19 PM

It only loads env vars into CommandBox's shell. looooong after Java has already started

👍 1

bdw429s

05/31/2023, 5:19 PM

You need to set that env var in your actual shell before ever running box

seandaniels

05/31/2023, 5:20 PM

I see. Thanks

bdw429s

05/31/2023, 5:20 PM

You can set them in a profile if you want so they always exist, or create a shell script called

box

that sets that and then runs the

real_box

, etc

bdw429s

05/31/2023, 5:20 PM

Or if this is a CI server, just run that set prior to running your build

👍 1

seandaniels

05/31/2023, 5:21 PM

all good. I'll just add that to my deploy shell script before it calls

box install

Open in Slack

Previous Next