this post was submitted on 05 Jun 2023
6 points (100.0% liked)

main

1450 readers
1 users here now

Default community for midwest.social. Post questions about the instance or questions you want to ask other users here.

founded 4 years ago
MODERATORS
 

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.

top 7 comments
sorted by: hot top controversial new old
[–] Thedogspaw@midwest.social 4 points 2 years ago

Nice seems to be running better good job on the maintenance

[–] lostbard@midwest.social 1 points 2 years ago

Every time I do database maintenance I think of this video. Godspeed. https://youtu.be/tLdRBsuvVKc

[–] Arindrew@midwest.social 0 points 2 years ago (1 children)

Well, we're still here. Which means it was successful?

[–] seahorse@midwest.social 1 points 2 years ago (1 children)

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@midwest.social 2 points 2 years 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.

[–] naeap@sopuli.xyz 0 points 2 years ago (1 children)

hi there!

could it be, that this is linked with the issue described on beehaw?

https://beehaw.org/post/446990

[–] seahorse@midwest.social 2 points 2 years ago

I'm sure it's at least somewhat related but it seems to be specific to my database.