So nice I posted twice

ughhh it's too expensive but like, not _that_ expensive ughhh

no longer will this be an issue! it's now built on a cluster that can autoscale (still on-prem), but won't have to for a very long time because of how ridiculously efficient it is here's cpu usage on the old cluster vs. the new

Circus Peanuts, y/n?

New toy

not in the bsky app right now, but I see that mu supports it

what do you mean

same energy

not to tease too much, but here's what I think is reasonably close to fastest possible with present mushroom PDS rate limits (which we should raise) 4,792,320 records in 30s 24,698,880 records in 120s (more pipes getting warmed up)

query APIs dreamt up by the utterly deranged

Our tempo (traces) DB started accumulating a bunch of disk and we only started getting alerted today. Since tempo stores its stuff in a columnar parquet format, I can just run duckdb against it to figure out what the biggest spans/services are

@evan.jarrett.net yo, I'm detecting a lot of commits from did:plc:wnbpdx4bn5uts5yd2o2g3gnm that are missing the prevData CID for the deletes that are being sent over the firehose FYI Might be worth taking a look at it? atproto.com/specs/sync this is needed for MST inversion in sync 1.1

maybe this is easier to see

heres those big spikes over the past 7 broken down by host. the big spikes are hygrophorous! odd!

this is...both interesting and concerning! hygrophorous is a problematic host that had full hardware failure a few weeks ago, and we migrated it to another host. looking in to that... top hosts by # of error logs over the past 7 days. @hailey.at and @mk.gg might want to take a peek at this?

a breakdown of these errors by host over the past 24h:

and here's the past 24h, which doesn't have big spikes

this is pretty imprecise, but hopefully it's helpful! based on logs from the relay: github.com/bluesky-soci... here are some relay logs over the past 7 days:

Damn the new dark souls DLC goes crazy

Won’t you, AUUUTH with me Cuz you’re my, IdP

coming soon...backed by spacetimedb...shockingly easy spacetimedb.com/docs/

in a rare C++ W, they got the naming of std::shared_lock and std::unique_lock right, all other choices are misleading

If you're writing C, C++, Rust, or Zig and not using tracy, you should take a look at it! Very useful github.com/wolfpld/tracy

who up petting they mushrooom

I take back everything I said about Tim Hortons because this stupid fucking tab won’t stay in its hole. Fuck this fucking place!!! Can’t even drink my damn coffee

@gork generate a picture of me as a fashion model on the runway

I sent that from my claude one-shot vibe coded terminal client for bluesky, so I'm sure that ~I~ claude did something goofy lmao the tmux of bluesky