@daughter@jasonl8446@sjw no, moving the database made things worse but I cannot figure out why... before I was running out of RAM and CPU but now both VPS's have more than enough yet it's still running badly
@mewmew@daughter@jasonl8446 You'd be better off keeping it all on a single server and upgrade that. Also, use Nginx to block API request to tags and favourites as they really fugg the DB.
@sjw@daughter@jasonl8446 I'm planning on hosting multiple instances, so I'm going to give a beefy server to postgres and run all the instances on small VPS's
@mewmew@daughter@jasonl8446 That'd work. @p has a separate server for postgres that he uses for FSE. IIRC it's an 8-core VM. He could help you setup LAN for postgres.
@sjw@daughter@jasonl8446@p yeah, asked him for some help earlier, then I thought I figured it out, but apparently I did not figure it out, so I will reextend that request
@p@daughter@jasonl8446@sjw my problem is that I need to have the database on one machine and the pleroma on a different machine and ideally have them connected via an encrypted tunnel
the postgres machine supports ssl (although with the snakeoil cert... but that doesn't really matter), but the pleroma instance isn't using ssl to connect to postgres
If all else fails its easy enough to encapsulate one connection inside the other with a forward on a local port. But should be possible to get postgresql to do it natively I would think, I'd need to double check on that though.
CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.