Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Database got overloaded 2025-01-14 #742

Open
peterdudfield opened this issue Jan 15, 2025 · 4 comments
Open

Database got overloaded 2025-01-14 #742

peterdudfield opened this issue Jan 15, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@peterdudfield
Copy link
Contributor

peterdudfield commented Jan 15, 2025 •
edited
Loading

Our production database got overloaded,
what seemed to help is updating caching in the API to 1.5.68

And running Vacuum Analyze on the database

Did not see this on dev.

other options for the future

  1. Only store a weeks worth of gsp data?
  2. tune other postgres parameters
  3. upgrade databse to latest, 16.6.
@peterdudfield peterdudfield added the bug Something isn't working label Jan 15, 2025
This was referenced Jan 15, 2025
Merged
Merged
@peterdudfield
Copy link
Contributor Author

Upgrade dev to 17.2 postgres

@peterdudfield
Copy link
Contributor Author

I noticed that when i upgrade the dev database to 17.2 it got slow, but then ran Vacuum Analyze on it. This might need to be run eveyrtime we upgrade the database to a new engine

@peterdudfield
Copy link
Contributor Author

blend=1.0.5 will help a bit

@peterdudfield peterdudfield changed the title Database got overloaded yesterday Database got overloaded 2025-01-14 Jan 16, 2025
@peterdudfield
Copy link
Contributor Author

  1. Default gsp/all to not give history
  2. UI could only pull the timestamp that its showing, not full timeseries - think this will be <1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@peterdudfield