30 day battle records

Jump to navigation Jump to search
Revision as of 31 January 2013 at 16:14.
The highlighted comment was created in this revision.

30 day battle records

I know I can't compete with giant clusters like bwbaugh, and it's not that scientific since it depends on what bots are submitted, but in case anyone's curious.. In September, I ran my i7 with 4 clients all month to see what I could max out at for battles contributed. Best I saw in "last 30 days" was 1,269,511.

    Voidious19:53, 26 January 2013

    I know my client spends more time on the upload than running battles, not sure if it's due to the extra latency from South Africa or just Darkcanuck's delays. That slow upload was one of my motivations for writing Literumble.

      Skilgannon07:53, 27 January 2013

      I built a custom results uploader which uploads battle results in parallel. Up to 15 simultaneous connections (configurable) are made to the server to work around latency issues. It makes a huge difference in melee, and also helps in 1v1.


      As a side effect, priority battles are downloaded in parallel, and they are grouped together before writing them in the priority battles file.

      If anyone is interested I can put it in the tools page.

        MN14:12, 30 January 2013
         

        I think it would be better to just allow both the server and the client to upload them in bulk, rather then one at a time.

          Chase14:45, 30 January 2013

          It would be a lot more efficient to have batch uploads, but the work around above at least keeps backward compatibility.

            MN15:50, 30 January 2013
             

            Keep in mind that the delays in uploading to Darkcanuck's server were added intentionally because the server couldn't handle the load otherwise. So it might not be a great idea to circumvent them. But I do agree that they take a lot of time and it would be great to have a system with faster up loads.

            On that note, maybe we should finally accept that Darkcanuck's server is "orphaned" and we need to setup a new one where we can update country flags / give people API access and so forth.

              Voidious15:53, 30 January 2013

              I think the biggest problem with Darkcanuck´s server right now is the admin, Darkcanuck, not being around. If the server suddenly goes offline for any reason, no one will be there to look after it.

                MN17:07, 31 January 2013
                 

                That might be an idea, and while we are at it we can add support for bulk transfers at least to the server. Perhaps a modified url for bulk download of robot pairings as well. This should cut off considerable time required to run the rumble, as sometimes the uploading can take as long as just running the battles.

                My feelings are split on if we should use the normal rumble or the lite rumble codebase. I like the idea behind the lite rumble, but python leaves much to be desired in the area of performance.

                  Chase01:16, 31 January 2013

                  I would prefer Java EE, but there are a lot fewer clouds which support it.

                    MN17:14, 31 January 2013
                     

                    I'm not sure we really need any special casing of bulk uploads. The uploads already fly with LiteRumble with whatever he's doing now.

                    I'm also torn, as Darkcanuck's server has a pretty robust feature set and is time tested with the huge load of a real rumble server. But I don't think it would be hard for LiteRumble to gain the new stuff we want and I love how lean and flexible it is. It's also a code base someone active is familiar with. And I'm happy to pitch in for resources if we need anything to support "rumble scale".

                      Voidious04:20, 31 January 2013
                       

                      Bulk uploads would be particularly nice for melee, because it would mean I wouldn't have to do as many database writes. But as far as upload speeds go, Literumble is way, way, way faster than Darkcanuck's server. Looking in his code, he has a 1 second wait hardcoded into each pairing upload, which is kind of ridiculous. That means that for each melee battle it takes a minute to upload once you count processing and connection overheads.

                        Skilgannon14:52, 31 January 2013
                         

                        In december I ran my i7 with one client continuously, it delivered 280k battles in 31 days. It also depends a bit on the priority battles to do, a new micro usually is faster and delivers more battles than f.e. a new XanderCat. I was proud on my 9000 battles a day, I remember the time when only David Alves could deliver more battles per month.

                          GrubbmGait14:33, 27 January 2013