@Chris (deprecated profile) @Jared Rhizor (Airbyte) did we double check that our Java connectors are actually using the entire RAM allocated to them in the Kube resources? Java's default behaviour is to use 1/4 of the host's container memory so I'm not sure the Java connector allows itself to use all the allocated memory

I'm guessing what this means is the connector uses 1/4 of the RAM allocated if it's specified

and 1/4 of the node's memory if it's not specified

I thought that wasn’t a problem after Java 10

https://developers.redhat.com/blog/2017/03/14/java-inside-docker is what I read on it

I didn’t test it though

yes those no longer apply

I'm thinking about this: https://www.baeldung.com/ops/docker-jvm-heap-size#1-automatic-memory-calculation

Ah

It’d be tricky to reliably specify custom memory reqs to different entrypoints / executables

Hmm

Haha yeah I punted on this by writing this issue: https://github.com/airbytehq/airbyte/issues/3440

so you’re saying that now that we can specify cpu/memory requirements to both docker and kube containers, these settings should be somehow forwarded to the jvm too?

yeap

we need to figure out a way to inject these via the

-Xmx

flag