One of the large applications I was working on had the same issue, to solve it we ended up creating multiple smaller instances and started hosting a set of related API's in each server.

for example read operations like list posts, comments etc could be in one server. write operations can be clusered in one server.

Later, whichever server is getting overloaded can be split up again. In our case 20% of API's used around 3/4th of server resources, so we split those 20% API's in 4 large servers and kept the remaining 80% API's in 3 small servers.

This worked for us because the DB's were maintained in seperate servers.

I wonder if a quasi micro-services approach will solve the issue here.

Edit 1: If done properly this approach can be cost effective, in some cases it might cost 10 to 20 percentage more in server costs, however it will lead to a visible improvement in performance.

Yea I started just using my clipboard alot, and hitting the x or back on jerboa and comments go thru at about 90% success rate. For posts I let it do its thing just incase. But been copying stuff to save as draft.

This issues is affecting other instances from what I can tell

My comments seem to not go through sometimes, whenever I upvote posts on Jerboa I get an error that just says timeout. Doesn't seem to happen on other instances.

Haha this just happened to me on my very first ever post to Lemmy and I was about to ditch this app. Not really. But I did copy my somewhat long post just in case. And I'm glad I did because I had to refresh and paste again and submit. However, within that issue, I found a weird bug. I had clicked on another post b4 going back to the thread that I wanted to re submit my comment. I checked out my profile to see my first comment and for some reason, my comment got posted on both threads, the related thread and the non-related thread. Devs might want to look into that one.

Nice teething problems. I tried to post to [email protected] but it just kept spinning. When I refreshed the post was not there.