SpeedTest often fails with "java.lang.OutOfMemoryError: GC overhead limit exceeded"

• when I run just that test class locally from IntelliJ, it runs ~20
  seconds, with small Metaspace/heap consumption

• on jenkins (there's maven module-level build parallelism with -T2),
  it runs 110-180s - no idea why it runs so much slower.

• I tried several time running identical command as is running on
  jenkins [2], including version of JDK and memory settings == xmx=2G:

• the Heap/Metaspace usage didn't get near the 2G maximum (see
  screenshots from VisualVM from 2 runs)
• the running time of that SpeedTest was 40-80s

• slaves used for full downstream build have 24G RAM + 8G swap, so
  lack of RAM shouldn't be an issue

• there seems to be no connection to the issue you mentioned [3]

• looking at history of this SpeedTest I see that you committed it
  initially as @Ignore, but Jozef later un-ignored it. Since this can be
  considered performance test and is failing randomly from time to time,
  I think we should mark it with @Ignore again.

[1] http://janhrcek.cz/random-failures/#/class/org.drools.workbench.services.verifier.webworker.client.SpeedTest/method/noConflictTable
[2] JAVA_HOME=/home/jhrcek/Tmp/jdk1.8.0_152 MAVEN_OPTS=-Xmx2g mvn -e
-nsu -fae -B -T2 -Pkie-wb,wildfly11,sourcemaps clean install
-Dfull=true -Dcontainer=wildfly11 -Dcontainer.profile=wildfly11
-Dintegration-tests=true -Dmaven.test.failure.ignore=true
-Dmaven.test.redirectTestOutputToFile=true
-Dgwt.compiler.localWorkers=1
[3] https://issues.jboss.org/browse/RHDM-488