Andrew Nesbitt

Yeah it looks like everything got really slow for a while like the server went to sleep almost, I will investigate

Even on this new server the database is totally overwhelmed! I've restarted it and things are working again but it's going to need some more tweaks to make sure it...

I'm running some background cleanup scripts on all the instances to remove a lot of unused database records, it may take a few hours and the dbs will be a...

Before running cleanup: The events table and it's indexes have grown very large and consume a lot of resources, the repository dependencies table is also very large and has a...

Cleanup is complete and I've also made a number of significant performance improvements across various parts of the app that should reduce database load on ipfs.ecosystem-dashboard.com (https://ecosystem-research.herokuapp.com) and I'll be...

There was a change earlier in the week to the pmf stats that has put a big load on the database, will see if I can tweak some things later...

@BigLep I have killed all the db connections and restarted everything, I think the next course of action will be to seperate the pmf stats from the issue triage as...

I gave the whole thing a big kick about 10 mins after seeing @BigLep's comment, and by big kick I mean: `heroku pg:killall` followed by `heroku restart` The problem is...

Yesterday I made some significant changes to the pmf calculations which should reduce the load on the database and keep the web ui performant.

The events table has grown very, very large and query time has reached over the 30 second heroku timeout limit. You can get the endpoint to load by removing the...