lxx.Tomcat 3.55 vs cs.ags.Scarlet 1.1c

Jump to navigation Jump to search
Revision as of 25 February 2012 at 21:48.
The highlighted comment was created in this revision.

lxx.Tomcat 3.55 vs cs.ags.Scarlet 1.1c

The duels between lxx.Tomcat 3.55 and cs.ags.Scarlet 1.1c are throwing OutOfMemoryErrors and crashing my clients.

I´m using the standard -Xmx512m parameter in a 64-bit Hotspot JVM (Oracle/Sun).

    MN13:50, 24 February 2012

    It's strange - i have no problems in same environment: java version "1.7.0" Java(TM) SE Runtime Environment (build 1.7.0-b147) Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)

    Can you do some more investigations (Tomcat vs Druss & Scarlet vs Druss etc. and see in which battles memory usage will higher) to detect which robot is eats memory and, if it's Tomcat. i will try to fix it

      Jdev03:35, 25 February 2012
       

      Scarlet uses lots of memory. The longer the battle the more memory used. So battles against top bots will use the most.

        Skilgannon06:53, 25 February 2012
         

        Made some tests. I set -Xmx2g, tested the pairings below twice each and tracked how much memory the JVM allocates:

        Tomcat vs Scarlet: 1,231,648k, 1,133,508k

        DrussGT vs Tomcat: 1,047,452k, 1,043,268k

        DrussGT vs Scarlet: 1,251,568k, 1,221,012k

        DrussGT vs Diamond: 869,356k, 878,216k

        Those numbers are maximum heaps. The actual used heaps are usually between 30% to 70% of those numbers.

          MN15:31, 25 February 2012
           

          So it seems both Tomcat and Scarlet use a lot of memory... hmm. I can see how a battle of one vs the other could cause problems on a memory limited machine. What are the maximum heaps used when run with -Xmx512MB ?

            Skilgannon20:24, 25 February 2012
             

            The reason Scarlet uses so much memory is it is just two bots that have been welded together. Each side manages its own information and systems.

              Chase-san22:48, 25 February 2012