for teamcity tests, use the same gc-related VM options as for production to get similar performance characteristics

This commit is contained in:
peter
2015-11-20 18:55:01 +01:00
parent f1f3e39d56
commit ddfc529abf
+3
View File
@@ -338,6 +338,7 @@ binding.setVariable("commonJvmArgsForTests", {
"-ea",
"-Dfile.encoding=UTF-8",
"-Dio.netty.leakDetectionLevel=PARANOID",
// yjpOptions("junit", "64"), // uncomment to start tests with a profiling agent (e.g. in a personal build)
"-server",
"-Xbootclasspath/p:${projectBuilder.moduleOutput(findModule("boot"))}",
"-XX:+HeapDumpOnOutOfMemoryError",
@@ -346,6 +347,8 @@ binding.setVariable("commonJvmArgsForTests", {
"-Didea.system.path=${p("teamcity.build.tempDir")}/system",
"-Xdebug",
"-XX:ReservedCodeCacheSize=240m",
"-XX:SoftRefLRUPolicyMSPerMB=50",
"-XX:+UseConcMarkSweepGC",
"-XX:-OmitStackTraceInFastThrow",
jdwp
]