If you are looking for a guide to help you choose which virtual #PostgreSQL talks to attend during the 4 @posetteconf#PosetteConf livestreams Jun 11-13, you're in luck! 🐔🐣
This is your ultimate guide 🧭 so you can plan & mark your calendar for POSETTE (& ideally join us for the virtual hallway track on Discord during some of the livestreams)
I am thinking of breaking #Postgres and #ElasticSearch to a separate server instead of increasing my current VPS resources.
I'll have two servers. My main, which will run Mastodon, and another that will have Postgres and ElasticSearch on it.
Will I benefit by doing this or should I just move ElasticSearch to its own server? What is the minimum CPU/ram I can get for the second server & what should I get?
@paul Yeah, it's a pain, and that totally lines up with my experience
For one of the big products at my job, literally over half of the hosting cost comes from ElasticSearch's RAM requirements alone. Every other microservice put together doesn't even come close to the RAM usage of just ElasticSearch. It's pretty insane for something that isn't, like, the core service being provided to customers
@paul i run my mastodon instance on two of Hetzner’s CAX 11 servers (ARM 64, 2 vCPU, 4 GB RAM) and they work very smoothly. One runs mastodon (incl Postgres) the other elasticsearch)
I’m not sure it makes sense to break out Postgres and elasticsearch onto the same server: both of these need quite a lot of resources, and I’d therefore like them on different servers. The one running mastodon would otherwise probably be quite idle (relatively speaking).
I split mine out primarily because I felt this gave me more resilience: any potential issues with elasticsearch (it hogging resources, needing scaling etc) wouldn’t affect my main mastodon experience.
🚀 I just published a short guide explaining how to upgrade PostgreSQL 🐘 from version 15 to 16 just after an upgrade to Ubuntu 24.04 LTS (Noble Numbat) 🦘