&zzz
+FreefallHeavens
+R4SAS
+RN
+ReturningNovice
+StormyCloud
+T3s|4
+acetone
+cims
+eche|off
+fa
+mareki2p
+nilbog
+orignal
+postman
+psychopuck
+qend-irc2p
+rednode
+snex
+wodencafe
Arch
Danny
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest81267
Onn4l7h
Onn4|7h
Over
Sisyphus_
Sleepy
T3s|4_
U1F642
Watson
Zapek
aargh4
ahiru
ananas
anontor
calamares
dr4wd3
duanin2
i2potus
ice_juice
justaperson
luvme
mahlay
makoto
marek22k
n2_
not_bob_afk
onon_
pinotto
poriori
profetikla
r00tobo
rapidash
test7363673
uop23ip
w8rabbit
x74a6
zelgomer
zzz
congestion caps broken in 2.3.0
zzz
//// remove after release ////
zzz
private static final boolean CONGESTION_CAPS = net.i2p.CoreVersion.PUBLISHED_VERSION.equals("0.9.58");
zzz
which makes it harder to tune the CapacityCalculator now
zzz
did y'all collect any stats on % D/E/G after the 2.2.0/2.2.1 rollout?
zzz
fixed, but this is irritating
dr|z3d
stats for congestion caps? I have them on the netdb summary page, working for me.
zzz
but do you have saved stats from the april/may/june timeframe before 2.3.0 came out and broke it?
dr|z3d
no
dr|z3d
just realtime stats.
zzz
I got about 0.2% D, 6% E, 0.4% G - you have similar?
dr|z3d
total routers in netdb = ~5K, D = 15; E= ~450; G = 25
zzz
ok I'm gonna get the % for 0.9.58 only so I can see the real nubmers
zzz
2% D, 11% E, 0 G
zzz
so this was going to be a key part of the congestion management improvements and attack mitigation for 2.3.0
zzz
and you guys gathered no data after 2.2.0 was out, did not incorporate it into the capacity calculator, and let it break
eyedeekay
I only started collecting stats after I started adjusting penalties, the only congestion cap related change that made it to 2.3.0 was to never pick G peers.
eyedeekay
So the reason I see so few D's and E's is because nobody was publishing them...