@eyedeekay
&eche|on
&kytv
&zzz
+R4SAS
+RN
+T3s|4
+acetone
+dr|z3d
+orignal
+polistern
+postman
+weko
An0nm0n
Arch
FreefallHeavens
Gid
Hikari
Irc2PGuest1893
Irc2PGuest4253
Irc2PGuest51480
Leopold
Minogami
Onn4l7h
Sleepy
Soni
T3s|4_
Teeed
aargh1
admin
anon
apt0110
b3t4f4c3__
cheddah
eyedeekay_bnc
idk
itsjustme
j6
limak
not_bob_afk
poriori
profetikla
qend-irc2p
rapidash
tbqdrn
theglitch
u5657
user101
wodencafe
x74a6
zer0bitz
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...