rampart creation/destruction in replay causes large cpu spike



  • This replay has a lot of ramparts being created and destroyed.

    https://screeps.com/a/#!/history/shard2/E55S4?t=14999427

    If I run that replay at 1 tick per second, Chrome browser is using about 8% of CPU, then each time a rampart is added or removed the entire replay stops playing for 0.5-1s, and the chrome cpu usage jumps up to 12% for a couple of seconds.



  • The same happens to any of my rooms in Steam client whenever rampart configuration is changed by adding/removing ramparts or making them public/non-public. Just seems to lock the client up for a non-insignificant amount of time.