Conversation
Notices
-
@theru It was working last night. Wake up this morning and PEAR errors all over.
-
Test of a restored backup. Something happened to mysql. Grrr!
-
@nybill :-P remember to do mysqldump
-
@theru I think I'll be going back to Linode. DO is quite slow and laggy. I wonder if that contributed to the problem. Like a mysql write failed midway.
-
@nybill I think it's Debian - Arch is so much better :-P
-
@theru There is that variable as well.
-
@nybill @theru #fightingwords
-
@nybill but anyway, I love Linode.
-
@nds Yea, I think I'll be moving back. (Actually I'm suing both right now and just point people to the right spot with A records.) Plus, I prefer Linode's user panel.
-
@nybill I had to double the RAM on #DigitalOcean to keep #MySQL / #MariaDB from crashing and allow software updates to complete. Considering moving both droplets to a single #Linode (where I've never had that problem).
-
fascinating. my 1024 MB Linode node is pretty tight, but mysql serving several web apps has never choked.
-
@lnxw48 DO also uses AMD where as Linode uses Intel stuff. I've generally found Intel chips are faster. This may play into things at on a server level as well. (Although I buy cheaper AMD stuff for my desktops.)
-
@nybill @nds more likely to be virtualization configs or how many VMs per hardware node