Content
@
0 reply
0 recast
0 reaction
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.
9 replies
22 recasts
122 reactions
jtgi
@jtgi
Great stuff. Nothin like a one liner. Thanks!
0 reply
0 recast
2 reactions