Gregory's Servermastodon.social has once again caught up with real-time. I haven't received the new machine for the database yet (seems like the technical issues unfortunately overlapped with some bank holidays; hopefully tomorrow) but I managed to find a way to optimize some code that seems to have helped. Thank you for being patient, and again, I'm really sorry you couldn't experience Mastodon at its best the past few days on here.
 @Gargron I don't know how much of this is running in memory, but if it is Linux there could be some small things giving performance gains.   @Gargron Nada de disculpas, por el gran trabajo que estás realizando para mantener Mastodon Social en pie. Gracias a ti por el tiempo y esfuerzo que has empleado en estos ajetreados días. Descansa y que el mastodon siga para delante. 😀👍🐘 @Gargron will the app be optimised to deal with the inevitable influx of migrant twitterati over the coming weeks and months?? I joined today and found both the app and website to be rather sluggish and unresponsive @Gargron totally new here so excuse my naive question: is there a waiting list for mastodon.social? Thanks! @Gargron I might help to optimize some DB queries and/or rewrite parts in C++ where it could improve performance. Where to start? @Gargron Still getting a lot of 502s and timeouts during peak hours at the moment on mastodon.online. @Gargron Thanks for doing this. It is great that we have a platform that doesn’t have a maniacal billionaire at the helm. |
@Gargron So my issues that I'm having on Tootstream is not of my doing? I normally access my "Home" "Fed" and "Local" no problem and even in the browser everything is hugely sluggish. I can access my "Home" (In Tootstream) after an interminable wait but no luck with the others, just times out. I'm on a 200Mbps fibre line so speed shouldn't be an issue. Thanks for any heads up that you could provide.