Yes, the server instances are definitely too large. I was previously running on 2 instances that were half the size and ran into some problems which I thought I could fix by increasing specs. Turns out the problems were not related to specs and now I'm stuck with the instance size (on DigitalOcean you can only up-size not down-size)
I use Postico too, but don't have enough SQL chops to get the answers I need.
* replace the currently inactive server with a smaller instance
* swap to the new instance and test the load
* replace the second server
For such a small app I’d drop the blue/green (most deploys will likely only take a few seconds?) and host Postgres on the same server.
Also, I’d move metabase onto a DO instance.
Any reason you’re using DNSSimple over a cheaper provider (or free in the case of DO)?
Getting to a place where you don't care as you can rotate in new instances at whatever spec you want is even better though.
The only thing I wanted to say is that the time spent learning a bit of SQL pays off massively. Perhaps something for your todo list :)
The graphs it generates are used both publicly (auto-updating):
https://sqlitebrowser.org/stats/
... and we have a bunch more private graphs and dashboards for metrics.
Everything is close to instant in responsiveness, apart from the "public" stats above. Those take some time to display purely on the browser side, as they feed way too much data to a browser for easy rendering. (will be fixed at some future point). ;)
Probably the only down side to Redash is a need to understand SQL. That can start out pretty simply though. :)
It is really great in situations where non-SQL people ask if you can run a query or report for them.
It is amazing how quickly you can build up instrumentation with it.