JayDi85
commented
11 months ago Just an idea - AI game can generates too much game events for watching/playing human. Server must send all that events for a client. It uses another thread for that task. Time to collect and send new game update is much larger than time for ai to play next priority, so that game update (game view creating) can catch concurrent modification error.
If true then there are possible fixes:
- Good: make thread safe game copy and use it for any callbacks instead real game (deep copy must be faster than all that rules generating code). Improved usage (???): create and store thread safe game copy by game itself, so any read only operations can use it instead a real game;
- Maybe good, maybe bad (also can used as additional network/traffic/cpu optimization): use game events queue for sending to client side and remove outdated events from it. It looks like current un-sync game updates logic from client side, but for a server.
phughk
Played a NEO draft, me and 7 AI. One of the AI v. AI games hung and never finished, nor was I able to watch it. CPU usage for one core is stuck at 100%. The following was in mageserver.log