You know that my preference is #5 as I want a galaxy with a slower tick rate.
#1 sounds like a smart practical idea. Does this data actually slow down the system that much just by existing on the same database? I’m guessing that moving it the first time will be an unmitigated mess, but that creating a script to move galaxy data when rounds end in the future would be a cleaner, automatic process.
#4 is the simplest to do naturally. Throwing money at a problem is not always the best answer though.
I don’t know what it’s up to. tick seems normal ,but having trouble navigating the pages after the tick. some testimonials from my fam.
Jets [Creator of P vs C]Today at 11:10 AM
Schnapp (MagicalSafetyDragon)Today at 11:10 AM
soo lagged out
Schnapp (MagicalSafetyDragon)Today at 11:07 AM it’s lagged out stupid game
GhostfacE (fart squirrel)Today at 11:06 AM I keep getting server error. Won’t let me log in Ahhh I have like 7 massive fleets out
Yep, the backend transition i’m working on will provide us with general performance gains, which will include both faster pageloads across the board + faster tick processing.
Also, we’ve since paid for a better-performing server, so we should see some additional improvements already, though I wouldn’t expect them to be lighting fast just yet. There’s still work to be done.