Farcaster Devs

fc-updates

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

The root cause was an expensive iteration. 

When a hub gets a message from a peer, it iterates over its entire peer store to track some stats. As the number of peers grew the iteration took longer and the number of iterations needed kept increasing. 

Eventually, the iteration couldn't be completed before the next one was triggered. This caused hubs to start crashing slowly. 

The fix was effectively a 1-line change that moved the iteration out of the critical path.

This one was tricky to track down. There were a lot of dead ends. Special thanks to 

@wazzymandias.eth for basically fixing it last night and not telling the rest of us 😂  

@cassie and @sds for some deep libp2p and tcp tuning magic, which we thankfully didn't need.

And finally to my good friend Claude, who pointed me to the `node --prof` command which is able to profile worker threads, would've been much more difficult to narrow down the root cause without it.

Building @warpcast and @farcaster. Previously Coinbase, Brigade, Causes.

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

one person's "libp2p tuning magic" is another person's "story written in blood just trying to make libp2p function"

I am now worried that we'll see libp2p by cassie out of spite for libp2p needing tuning

Developer 🤓 build, develop and operate Farcaster solutions @ dtech.vision also love tech, decentralization, fitness and oldschool rap 😎

I knew it 😝 hoping one day I‘ll be fast enough Engineering wise to do be on my „ah I‘ll just do it myself“ arc

That's already happening for libp2p-gossipsub, it's blossomsub v2.0