Clients do not update State to RUNNING on low-end machines with 1 CPU core

[davechurchill]

Clients do not update State to RUNNING on low-end machines with 1 CPU core

[davechurchill]

How many is several? The RUNNING status is detected by a file that's created by the Tournament Module, so if you're experiencing severe disk IO blocking then this may happen. It may also be a firewall issue? Not sure if Rick has any other ideas, but I've never come across this issue before

[w4tsn]

I tried it with 2 and 4 (one with Server and Client, the others only Client), but all on the same machine with 12 Cores and 32 Gb of RAM and the VMs virtual disks all residing on one SSD drive.

Yeah, IO could be blocked. When the VMs only have one core and therefore can't handle Java, Server, StarCraft and OS fast enough.

If the VMs are located on a HDD (which is fairly old and slow) it gets even worse. This way even 2 CPU cores per VM are not enough to handle the requests.

Firewalls are deactivated.

[davechurchill]

Okay, so it appears to just be an issue like you said when resources are extremely low on a single core, which sort of makes sense. I guess the tasks related to IO are super low priority behind the OS and Starcraft so 2 cores seems to be a must. @richard-kelly can you add a note in the documentation to say that 2 cores should be a minimum for each client machine?

Thanks for the heads up, however I'm really not sure that this is an issue that we can necessarily fix, so we'll just warn people instead :)