Weird rumble scores

Fragment of a discussion from Talk:BeepBoop
Jump to navigation Jump to search

You are right. Apart from creating many thrads that do a lot of work when it’s others turn, creating a lot of objects to increase GC overhead does affect others’ bots as well, making the result a little bit random.

But I doubt how much difference can GC overhead put. The most unreproducible scores I experienced are always coming from some rare exceptions, say 1/1000. And once happened, it causes some random pairing to be close to 0. If averaged with some normal score, it really looked like it’s decreasing with no reason.


But there’s always some reason, and mostly coming from specific bot instead of the clients, since not everyone is affected.

Xor (talk)20:36, 24 June 2021

For the specific case I mentioned of ags.Glacier 0.3.0 versus lxx.Emerald 0.6.5, when it was at 1 battle, I thought it was likely some rare exception as you say, but then a 2nd battle came in with about the same low score as the 1st battle, and yet I'm not able to reproduce a result anything like that in many many tests. This leads me to believe that there is most likely something significantly different about the environment those two battles were run in, as compared to my own environment.

Rednaxela (talk)20:46, 24 June 2021

I think there must have been a bad client running at some point. BeepBoop 0.14a is identical to 0.14, but is getting 0.3 points better in the rumble now. Even weirder, I just noticed that BeepBoop 0.13 has 85% against eem.awful, which disables itself at the beginning of each battle!

--Kev (talk)22:41, 24 June 2021

Let’s wait more battles, if the score goes down to some similar APS after ~30000 battles, then every body’s client is fine.

Xor (talk)02:31, 25 June 2021