Joe
11/01/2019, 12:14 AMgraphql-kotlin
1.3.0 vs 1.2.1: When running our unit tests on CircleCI, we're hitting the 4G max memory usage for a container limit. We can get around it by setting JAVA_TOOL_OPTIONS=-XX:MaxRAM=1g
, but somewhat concerned that this is newly needed? Has anyone else seen anything similar?Dariusz Kuc
11/03/2019, 3:31 PMJoe
11/03/2019, 9:44 PMDariusz Kuc
11/04/2019, 2:49 AMJoe
11/04/2019, 3:18 AMDariusz Kuc
11/04/2019, 3:29 PMClassGraph
vs Reflections
libsClassGraph
ends up loading more than intended -> when doing some local testing my memory usage went from slightly over 2GB for the graphl
tests to ~800MB after limiting the packages to scanJoe
11/04/2019, 4:37 PMSchemaGeneratorConfig(listOf())
with SchemaGeneratorConfig(listOf("java.lang"))
is still showing the error without a more restricted java memory usage setting; is that not a good way to narrow the scope or do we just need to tweak the mem usage settings better for the restricted CI environment?Dariusz Kuc
11/04/2019, 4:56 PMjava.lang
you should be pointing to com.trib3.graphql
or something like thatJoe
11/04/2019, 7:20 PMcom.trib3.graphql.subpackage
does pass without tweaking the memory settings fwiw