Oh also, some of the time to run the game is just waiting: 3 seconds to allow algos to setup, and 3 seconds after the game is over to allow time for things to close up. So a way to get a ton of games completed quickly would just be to parallelize running games locally since compute wise they are spending a lot of time waiting not computing anything.
Although, I do believe the error messages an algo prints out might get jumbled because it saves a temp file in the directory of the algo where it temporarily saves the errors. So if you have two separate games running with the same algo folders they will clobber the same error file. But the replays generated would be fine so this is only a concern if you want to train on things you print with debug_write. If you do need the error prints you could also just duplicate the folder of your algo a bunch to get around that so that every game is using a different algo folder. I’ll try to make it so the name of the temp error file generated has some random characters so this isn’t an issue in the future too.