Wompi: Reply to Initialization Code Runtime Reduction Effort

2013-02-17T11:04:55Z

Reply to Initialization Code Runtime Reduction Effort

New page

Well, I couldn't hold it and had to run some tests.

I tested all three collectors on XanderCat 12.3 vs Virus and Diamond vs DrussGT
<pre>
-XX:+UseSerialGC
</pre>
DvsD: both bots dropped turns like crazy and DrussGT almost ever won with 64% APS 
XvsV: XanderCat dropped constantly turns over all battle rounds (sightly more on the first two rounds) and lost quite a few rounds against Virus

<pre>
-XX:+UseParallelGC -XX:+UseParallelOldGC -XX:MaxGCPauseMillis=1
</pre>
DvsD: both bots dropped even more turns than with the SerialGC - DrussGT still won with 64+% APS 
XvsV: XanderCat dropped a lot turnes in the first round and some in the second - all other rounds had no skipped turns (because of the crummy first round he took the wrong movement and lost a bunch of APS vs Virus)

<pre>
-XX:+UseParallelGC -XX:+UseParallelOldGC -XX:MaxGCPauseMillis=30
</pre>
DvsD: less skipped turns for both but still to much - DrussGT still on 64% APS 
XvsV: no changes to 1ms pause

<pre>
-XX:+UseConcMarkSweepGC
</pre>
DvsD: DrussGT drops a turn here and there - Diamond still drops a lot turns but with a lower frequency - DrussGT wins with 50-55% APS 
XvsV: XanderCat stops dropping turns at all (just a few here and there) and wins against Virus with 99%
 

I also changed some other ratio settings but could not see any visible changes to the overall behavior. To me the concurrent collector looks quite promising and I think I play a litlte with the CMSIncremental.. options to see if there is still room for some improvements.

Thread:Talk:XanderCat/Initialization Code Runtime Reduction Effort/reply (14) - Revision history

Wompi: Reply to Initialization Code Runtime Reduction Effort