Database Migrated to a new server
Database Migrated to a new server
There was a period on an hour where we migrated our database to it's own server in the same data centre.
This server has faster CPUs than our current one, 3.5GHz v 3.0GHz, and if all goes well we will migrate the extra CPUs we bought to the DB server.
The outage was prolonged due to a PEBKAC issue. I mistyped an IP in our new postgres authentication as such I kept getting a "permission error".
The decision of always migrating the DB to it's own server was always going to happen but was pushed forward with the recent donations we got from Guest on our Ko-Fi page! Thank-you again!
If you see any issues relating to ungodly load times please feel free to let us know!
Cheers,
Tiff
If you see any issues relating to ungodly load times please feel free to let us know!
Right now loading every page -- except profiles -- seems to take about 2~3 seconds with occasional spikes up to ~10 seconds. (Profiles are much slower to load -- ~6 seconds typically and sometimes much longer.) I'm using the "old" (mlmym) interface mainly, but testing with the default interface seems to have similar performance with a lot of spinners on every action. It's not unusable but it's definitely noticeably slow.
Hmmmm that isn't great news. While testing it was working great, which is just my luck.
I can see that there are a lot more spikes now compared to before, and even when ssh'd to the server I can sometimes feel the lag.
I'll be investigating today as I really don't want to roll back to our single server again. There are probably some fine tuning items that need to be done on the network stack side now.