Weird rumble scores

Jump to navigation Jump to search

0.15 is getting also weird rumble scores. For example, this figure is showing some of the strange results.

BeepBoop 0.15 weird rumble scores.png

Does anyone know how to see who's producing the weird scores/debug?

--Kev (talk)23:07, 12 July 2021

That can only be Xor_Sily, that is the only one that has run battles in after you uploaded version 0.15

Did you manually set the CPU constant in your robocode install ? Maybe Xor has to recalculate the CPU constant for Xor_Sily, if the machine it is running on has become heavier loaded.

GrubbmGait (talk)23:16, 12 July 2021

No, I just used the auto-computed constant.

--Kev (talk)00:31, 13 July 2021
 

The cpu constants of Xor_Sily is computed when all cores are used, and currently I’m using only half of the cores as suggested by Rednaxela. So maybe the cpu constant is a little bit loose, making skipped turns happen LESS. If a bot isn’t skipping turns in ordinary configuration, it shouldn’t skip turns on Xor_Sily.

If anyone is logging data, I could help by sending the files.

Xor (talk)10:23, 13 July 2021

Isn't using half of the cores also half the performance, so taking twice the time, so ideally twice the cpu constant ?

GrubbmGait (talk)22:38, 13 July 2021

cpu constant is always single core. by all cores / half cores I’m describing number of clients running concurrently, since GC is also requiring some cores.

Xor (talk)04:56, 14 July 2021
 
 

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:BeepBoop/Weird rumble scores/reply (27).

I'm not sure I follow: what you are saying suggests that skipped turns should happen more on Xor_Sily right? I assume the reason for BeepBoop's low scores is it skipping lots of turns.

--Kev (talk)18:59, 14 July 2021

As an aside, I've also noticed that DrussGT 3.1.7 has also dropped 0.3 APS compared to 3.1.6, maybe it is also getting bad battles with lots of skipped turns?

--Kev (talk)19:01, 14 July 2021

I think it’s some change to energy management. Skipped turns hurt results against weak bots as well, but the decrease seems to be focused near 60+

Xor (talk)04:38, 15 July 2021
 

I mean if you run battles on computers without turbo boost, you should get identical results as Xor_Sily.

Xor (talk)04:36, 15 July 2021

Hmmm I'm still not able to reproduce the low-scoring battles. First of all, turning off turbo boost does change the CPU constant for me (it's ~4e6 with turbo boost on and ~5e6 with turbo boost off, I've recomputed the constant both with/without multiple times and it seems reasonably consistent). But even if I use the 4e6 CPU constant with turbo boost turned off, I am getting essentially the same results as in the image I uploaded. What CPU constant does Xor_Sily use? Maybe as a short-term fix you could add BeepBoop to its roborumble.txt EXCLUDE?

--Kev (talk)08:00, 15 July 2021
Edited by author.
Last edit: 18:39, 15 July 2021

I stopped Xor_Sily. It's some high performance server that costs $40 a week. Maybe we need some test set to verify rumble clients before entry, making it easier to serve a client.

Btw, could you re-submit a version and run rumbles on your machine, and see if we can get the correct result now?

Xor (talk)17:56, 15 July 2021

I think the problem is that Xor_Sily is running 7/24, for months. If memory leak happens, GC will get worse and worse. Maybe I should add some auto restart script later and try again.

Xor (talk)18:10, 15 July 2021

You can set the max iterations in the client and run it in a bash loop.

Skilgannon (talk)23:44, 15 July 2021

Great suggestion. I will try after BeepBoop get some stable result.

Xor (talk)05:41, 16 July 2021
 

What sort of high performance server is this? If it's virtualized rather than true dedicated, it wouldn't surprise me if the exact amount of available CPU varies dramatically from moment-to-moment even if the provider is guaranteeing some number of cores worth of overall performance.

Could be interesting to some time make a tool for measuring the stability of available CPU, based on running rapidly running a series of identical micro-benchmarks and looking at the variations in how long it takes.

Rednaxela (talk)10:54, 16 July 2021
 
 
 
 
 
 
 

Looks like the weird battles are produced on Xor_Sily. I will run some battles using these bots manually on Xor_Sily, to see what's happening.

Btw I'm not experiencing weird results personally, battles ran in local have similar results in rumble. How many cores are u using when running local battles?

Xor (talk)10:35, 13 July 2021

Thanks for looking into it! I'm using 4 cores when running local battles.

--Kev (talk)19:39, 13 July 2021

Another info, are you using turbo boost enabled computer? I suspect this makes cpu constants inconsistent. Since cpu constant mostly happens when load isn’t high and turbo isn’t enabled.

Xor (talk)06:32, 14 July 2021

Yes, I am running on a turbo boost enabled computer.

--Kev (talk)18:58, 14 July 2021