Just in case you were not in game

[Thatcher]

Ten bucks on terraforming.

I second that shiz.

[Phazaar]

What was said was that it's specific actions that necessitate a backup ending up bottle-necking the data the more they're queued. The fix will not be to slow terraforming/whatever else down 10 fold (or at least, shouldn't be). The checks they're putting in place are to allow them to monitor specifically what is happening at the bottleneck(s) and find a solution in the code. Let's hope it doesn't take much longer, eh?

[Marcolo]

What was said was that it's specific actions that necessitate a backup ending up bottle-necking the data the more they're queued. The fix will not be to slow terraforming/whatever else down 10 fold (or at least, shouldn't be). The checks they're putting in place are to allow them to monitor specifically what is happening at the bottleneck(s) and find a solution in the code. Let's hope it doesn't take much longer, eh?

Sounds like a database update issue to me. Database updates generally are some of the most expensive processes that can run.

Since commits to a database lock and block, the update queue to commit can get huge if certain "actions" require a lot of time proportionally, which in turns starts eating up server resources and slowing down reads. Eventually the server cache is waiting much longer to grab clean data from the database.

This could explain why rollbacks happen automatically when the server is reboot, and why latency can increase and decrease sporadically. It also has almost nothing to do with the number of servers or the bandwidth, and is more about tuning individual actions that require database updates.

NOTE: It's also complete garbage since I have no concept of how this game is programmed. But, admittedly, it is fun to guess. Regardless of what the real issue is, sounds like they are working hard, and I hope they are able to find and fix it soon.

[wyldmagik]

You may not have a concept on its programming, but adding debug routines in an all ready buggy and lagging to death code, WHILE in launch phase and paying customers is priceless

[Vysara]

You may not have a concept on its programming, but adding debug routines in an all ready buggy and lagging to death code, WHILE in launch phase and paying customers is priceless

Or they could just leave it and not fix it, yeah?