What happened 

Sidekiq fell thousands of jobs behind (about an hour worth of posts) due to the Wasabi lag, as Sidekiq was waiting on media uploads/downloads for federation.

I decided to try and fix this by switching temporarily to local media, taking advantage of our existing proxy to fall back on Wasabi when it's not available locally.

While trying to implement this, I was bitten by someone upstream making the horrible decision to move Webpacker compilation into the Docker build step, so I was waiting on Webpacker compiles just to make VERY BASIC config changes. I reverted those changes and got the proxy system working, but still had to wait for another Webpacker compile, as previous compiles were put into temporary container storage and were lost. This compile is being done to a shared volume.

Any new media will be reliable as it's not being served from Wasabi. Any old media will be unreliable until it's brought into our cache. If we exceed 32G of media in the cache the least recently used pieces will start being evicted, as before.

The Webpacker compile took nearly 30 minutes.

Follow

@announce I managed to bring down webpacker times from 30min to 12 by disabling js minification, maybe that helps you

Sign in to participate in the conversation
Awoo Space

Awoo.space is a Mastodon instance where members can rely on a team of moderators to help resolve conflict, and limits federation with other instances using a specific access list to minimize abuse.

While mature content is allowed here, we strongly believe in being able to choose to engage with content on your own terms, so please make sure to put mature and potentially sensitive content behind the CW feature with enough description that people know what it's about.

Before signing up, please read our community guidelines. While it's a very broad swath of topics it covers, please do your best! We believe that as long as you're putting forth genuine effort to limit harm you might cause – even if you haven't read the document – you'll be okay!