Weird rumble scores

Fragment of a discussion from Talk:BeepBoop
Jump to navigation Jump to search
Edited by author.
Last edit: 17: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)16: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)17:10, 15 July 2021

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

Skilgannon (talk)22:44, 15 July 2021

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

Xor (talk)04: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)09:54, 16 July 2021