hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

8.9K
active users

#mastadmin

1 post1 participant0 posts today
Replied in thread

@KuJoe

Our instance runs on @netcup's VPS 3000 ARM G11, i.e. a 12 core KVM VM on Neoverse-N1 #ARM64 server hardware.

We don't have a lot of users yet. However, when users with >1K followers moved to our server, the #sidekiq queue did grow (running the default install of Mastodon, no Docker).

So we used the opportunity to do the configuration tuning that had worked well when some of us scaled an AMD64-based Mastodon instance previously: create several sidekiq processes by copying and adapting a systemd service file – roughly as detailed by @leah here: leah.is/posts/scaling-the-mast
This sped up sidekiq enormously – as it had done earlier on different hardware.

To sum up, we highly recommend ARM hardware for running Mastodon instances because it eats less energy and performs well enough.

leah.isScaling the Mastodon - Leahs Gedanken
Continued thread

It looks like I finally managed to resolve this by increasing postgres’ max_connections setting, together with introducing the DB_POOL setting in my Mastodon enviroment:

blog.thms.uk/2023/07/tweaking-

I have no idea why this was suddenly required, when Mastodon was running just fine previously, but it does seem to have resolved it.

Thanks everyone who tried to help me, and especially to @mwadmin for pointing me in the right direction.

blog.thms.ukTweaking Postgres for Mastodon - blog.thms.ukI had to increase Postgres' max_connections settings to resolve issues with my Mastodon instance.

Life of a #sysadmin - #mastadmin. Tweaking some things about my instance while updating servers in an old environment that i'm trying to slowly migrate away from at work. I really do love what I do and when people ask, I can't really imagine a life outside of what I do every day.

Here’s another case of why I’m building Tusk (as I’ve come to call it):

From @simon :
“My least favourite sharp edge of Mastodon is the fact that when you view someone else's post you only see replies to it that are known to your server - so there's actually a good chance there will be replies that are completely invisible to you, especially if you run your own instance”

#MastAdmin #SingleUser #discoverability

fedi.simonwillison.net/@simon/

MastodonSimon Willison (@simon@simonwillison.net)Content warning: Mastodon meta

#Mastodon #Admin help please.

I'm running my own instance with just 2 users. Admin and 1 real.

Checking my media usage I'm seeing this

Attachments: 18 GB (11.1 MB local)
Custom emoji: 74.5 MB (0 Bytes local)
Preview cards: 449 MB
Avatars: 2.02 GB (76.5 KB local)
Headers: 4.67 GB (98.7 KB local)

I tried tootctl media remove but that does not seem to remove the "non-local" attachments etc.

Am I missing something here?

Replied in thread

@tfiebig Thanks! I think I've found a few things...

* I did not set up Elastisearch. I'm on a cheap instance, don't want to hammer it. Once I get a few more onboarded we'll see.

* Because of federated, we just have to rely on trending hashtags, or manually go to other servers (list at joinmastodon.org/servers) to search for content

* Trying to get 'relay' setup with other servers... gonna be a key element if people don't want to be silo'ed.

joinmastodon.orgServersFind where to sign up for the decentralized social network Mastodon.