After making my #framework laptop my daily driver, I still had to fix all the #electron applications looking like crap under #wayland (when using fractional scaling).
So another good reason to make a blog post, I guess? :ablobcathappypaws:
Slack, Discord, Spotify, Obsidian, VS-Code, ... now they all look good using 1.25x scaling.
Even though there's no need at the moment, I'm doing some tests to scale the Mastodon instance of BSD Cafe. I'll likely tweak some settings to be "ready" to spin up additional support jails or services if needed.
I won't be using auto-scaling techniques but rather the good old method called stefano-scaling.
Does anyone have favorite stories of scaling popular web services ca. the late 90's / early 00's they could link to? (e.g., bradfitz's livejournal scaling story 1!)
Any #MastoAdmin have ideas how mastodon.social plans to scale? With the sign up focus on them for ease of onboarding - if it works - could see their numbers grow rapidly. I hope it forces them to find ways to optimize. Otherwise all their donation $$ will go to cloud costs and mobile development while I wish it was all focused on Mastodon development.
@thedarktangent sure. It depends how the software scales out right now, but I imagine it's still fairly naïve. My theory is that the actual behind-the-scenes work pulling data from all other federated instances takes quite a bit of processing power and bandwidth. It would be wise to break this out to a separate vertically scaled service while the day-to-day handling of user requests is scaled out horizontally.