Huge battle results file?

Jump to navigation Jump to search

Huge battle results file?

In literumble stats I see that one of my rumble client has stopped working for a few days — and once I had a look, it shows

929073875 Jul 2 21:40 resultsmelee.txt

the resultsmelee.txt grows so large that even the JVM gets killed when processing the file (887M)

and the content of the file is just one line which gets duplicated all the time (which grows exponentially).

Not sure whether this bug is fixed in the newest version, or how can I send pull request to robocode base? the github code seems to be mirror only.

Xor (talk)07:11, 5 July 2018

I would suggest making a bug on Sourceforge and attaching a patch if you have a fix.

Skilgannon (talk)20:19, 5 July 2018

Thanks ;)

The patch is submitted:

Xor (talk)05:43, 8 July 2018

Btw, is literumble affected by duplicated uploads? Will it remove duplicated battles automatically?

Xor (talk)06:06, 8 July 2018

Literumble will reject battles older than 24 hours, so any broken battles have a limited window of problems.

Skilgannon (talk)09:40, 8 July 2018

Thousands of duplicated battles could be generated within only a few minutes due to the fact of exponential growth. Thankfully this only happens to bots with multiple weight classes. If literumble is not removing duplicates, then this could answer why some bots get 2x or 5x more battles than other bots. And for those bots, their battle result is mainly determined by those duplicated record which causes inaccurate score ;(

Hope fnl should react sooner this time (instead of half a year)

Xor (talk)11:25, 8 July 2018

Only that pairing will have lots of battles - it won't affect the score that much, since it doesn't affect all the other battles. Also, pairings are weighted with a rolling average so roughly only the last 40 battles actually contribute. So once some more battles happen it won't matter.

Skilgannon (talk)11:34, 8 July 2018

That’s a really nice design ;) Rolling average just deletes outdated battles smoothly.

Xor (talk)11:39, 8 July 2018