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.
10 replies
7 recasts
44 reactions

Sanjay pfp
Sanjay
@sanjay
@adityapk knows what I'm talking about
1 reply
1 recast
10 reactions

Aditya Kulkarni pfp
Aditya Kulkarni
@adityapk
Our mutual friend Claude has gotten pretty good recently.
1 reply
0 recast
2 reactions