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
jj ๐
@jj
Itโs kinda crazy - Iโm now seeing over 10k+ peers and still going Awesome job team!
2 replies
0 recast
1 reaction
jj ๐
@jj
@sanjay just finished a scan and itโs 16k+ peersโฆ
2 replies
0 recast
1 reaction
Sanjay
@sanjay
Thatโs insane. Are you counting unique peer ids? Via getCurrentPeers?
1 reply
0 recast
1 reaction
jj ๐
@jj
Yes ill upload it again with ip traces
0 reply
0 recast
1 reaction