Hello, you’ve probably experienced slowness and timeouts recently and I’m going to try to fix it by backing up the DB, blowing it away, and then recreating it from backup. Wish me luck.
- PenguinCoder ( @Penguincoder@beehaw.org ) English11•1 year ago
Good luck. Stop the DB processes before you backup :P
Thanks for reminding me lol
- The dogspaw ( @Thedogspaw@midwest.social ) English4•1 year ago
Nice seems to be running better good job on the maintenance
- Arindrew ( @Arindrew@midwest.social ) English2•1 year ago
Well, we’re still here. Which means it was successful?
I was able to rebuild the DB but there’s still the CPU spiking issue with postgres which causes the site to slow way down.
- WithMeDoctorWu ( @WithMeDoctorWu@midwest.social ) English2•1 year ago
Been a few years but if I recall correctly the postgres “out of the box” settings are extremely conservative with regard to memory usage, to allow implementation on minimal hardware. (That might have changed in the last few years.) Once there’s significant data flow, some of the params need to be jacked up to run smoothly.
Disclaimer, I’m certainly no expert, and you might already know more about this than I do.
- lostbard ( @lostbard@midwest.social ) English2•1 year ago
Every time I do database maintenance I think of this video. Godspeed. https://youtu.be/tLdRBsuvVKc
- naeap ( @naeap@sopuli.xyz ) English2•1 year ago
hi there!
could it be, that this is linked with the issue described on beehaw?
I’m sure it’s at least somewhat related but it seems to be specific to my database.