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.
9 replies
22 recasts
122 reactions

jj 🛟 pfp
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 🛟 pfp
jj 🛟
@jj
@sanjay just finished a scan and it’s 16k+ peers…
2 replies
0 recast
1 reaction

Sanjay pfp
Sanjay
@sanjay
That’s insane. Are you counting unique peer ids? Via getCurrentPeers?
1 reply
0 recast
1 reaction

Agadoo 🎩 pfp
Agadoo 🎩
@agadoo
Don’t know if such a thing exists (or is possible to find out either from hub data or maybe FC team) but I’d be fascinated to see a graph of number of hubs over time (I.e. when did the spike start). Am assuming it’s a proper ‘vertical line farmer’ spike too
0 reply
0 recast
0 reaction