The most memory-hungry nodes in the Tranquility cluster, the Character Services nodes that store those brains I mentioned above (among other things), were at 75% memory pressure at the end of day #2 last time, which is just below our operating tolerance of 80%. We also never clean up any memory, as the cluster node memory is reset every day anyway, which is a reliance on a daily reboot (note: we of course don't clear our DB cache memory or our Redis cache memory, but the main simulation cache memory is cleared in the reboot in each downtime). As an example, the Brain in a Box and Dogma Rewrite projects in 2015 were all about computing and storing skills and their effects (i.e., the characters' brains) and transferring the computed results between solar systems instead of re-computing the brains on each entry to a new solar system. For better performance, then, we have always opted for pre-computing values & processing data and storing the results for later reference rather than re-computing those values again later. Tranquility has always been memory hungry. Time desynchronization is now normally within ☑/100 of a second, well within the maximum of ☐.5 seconds. Players started to notice once the desynchronization was above 3 seconds, mostly by noting what felt like module lag or delay when their client and the node hosting their solar system disagreed significantly about when modules were cycling. But with newer hardware, we had been observing an end-of-run desynchronization of 2.25 seconds and - predictably - 4.5 seconds at the end of day #2 in the first no-downtime experiment in 2019. The target for time desynchronization is a maximum of ☐.5 seconds. The time desynchronization was a known issue, but last time we were observing whether players noticed at the end of day #2. We also observed time desynchronization (which we fixed), and significant memory usage (which we improved somewhat). Now we want to verify them further (of course they have been tested but our test environments don't have Tranquility's scale) and look for more such issues. We fixed all those issues that we found, and those you reported to us. So what did we discover last time, I hear you ask?įirst and foremost we discovered reliance on downtime as an event to mark the beginning of a daily cycle, and a reliance on a daily startup, such as structures not finishing 24+ hour timers and corporations not joining Faction Warfare.
There is a (soft) lower bound of approximately 3 minutes given the three different activities during downtime - shutdown, database jobs, startup - which last approximately 1 minute each, unless fundamental changes are made, and the most fundamental one is still to not have any downtime at all. The purpose of this article is not to comment on that decision either for or against*. Read this articleĪs everybody who pays attention to EVE-related news knows by now, CCP is raising the price of EVE Online (both Omega subscriptions and PLEX). After more than 14 years, I have biomassed everything, and a GDPR purge request is pending with CCP to delete my eight accounts. On May 4, 2022, I logged into EVE Online for the last time. What follows below is the text of the speech given by The. Read this articleġ8 months after the last address, given just ahead of the battles of M2-XFE, a State of the Goonion (SOTG) was held on June 19 at 1800 UTC.
He is replaced in GoonWaffe by Interim CEO TheAdj, and an announcement. Earlier today, in an alliance ping and a post to the Goonfleet forums, The Mittani officially resigned as the Executor of Goonswarm Federation and corporation CEO of GoonWaffe.
0 kommentar(er)
