Has anyone come up with a strategy for load testing a Mastodon instance? I’d love to run some tests around how much traffic my setup can handle *before* it breaks organically.
Conversation
Notices
-
Embed this notice
Philip Mallegol-Hansen (philip@mastodon.mallegolhansen.com)'s status on Wednesday, 07-Aug-2024 22:41:08 JST Philip Mallegol-Hansen - BeAware :fediverse: repeated this.
-
Embed this notice
BeAware :fediverse: (beaware@social.beaware.live)'s status on Wednesday, 07-Aug-2024 22:41:07 JST BeAware :fediverse: @philip well, it can't be done by request unless you know some "bigger" accounts.
Basically just by having a bigger account boost your post, it can stress the instance.
I can attempt to help by boosting this but I am still small compared to some others here.
Maybe some in my follow circle can help as well, to see if we can bring your instance to it's knees?😅
-
Embed this notice
BeAware :fediverse: (beaware@social.beaware.live)'s status on Wednesday, 07-Aug-2024 23:01:43 JST BeAware :fediverse: @paul @philip there's a relay? 🤔
I had used a relay that brings their posts to my instance, which causes the same thing, but it's not official, it's relay.fedi.buzz 🤷♂️
-
Embed this notice
Paul Chambers (paul@oldfriends.live)'s status on Wednesday, 07-Aug-2024 23:01:44 JST Paul Chambers Subscribing to the Flipboard relay with 4 CPU cores and 6 GB RAM, even with jvm memory set at 1gb, brought my ElasticSearch down at around 1pm every other day and crashed Redis also. It's a busy relay.