Content pfp
Content
@
0 reply
0 recast
0 reaction

Sanjay pfp
Sanjay
@sanjay
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.
6 replies
4 recasts
35 reactions

WhizKid pfp
WhizKid
@befriendh3
Definitely a rollercoaster! 🙌 Huge props to @wazzymandias.eth for the stealthy late-night miracle 😂 Hats off to @cassie and @sds for the libp2p and tcp wizardry, even if we didn't need it. And big thanks to Claude for pointing out `node --prof` — worth its weight in gold for troubleshooting! 🚀
0 reply
0 recast
0 reaction