~dr|z3d
@RN
@ReturningNovice
@StormyCloud
@eyedeekay
@orignal
@postman
@zzz
%acetone
%mareki2p
%snex
+Atticfire
+FreefallHeavens
+Onn4l7h
+Onn4|7h
+Over
+fa
+marek22k
+onon_
+poriori
+profetikla
+qend-irc2p
+r00tobo
+sexy
+uberius
+uop23ip
Arch
Danny
Irc2PGuest21708
Irc2PGuest28384
Irc2PGuest66257
Irc2PGuest75631
Irc2PGuest99986
Meow
RTP_
T3s|4
T3s|4_
U1F642
Watson
ahiru
anontor2
cims
i2potus
interesting
justaperson
lokzz
luvme2
mahlay
makoto
n2_
nilbog
not_bob_afk
pinotto
r00tobo[2]
rednode
user_ygg2__
onon_
Look at the uptime of user1, who can do the same?
onon_
6 days without disconnections.
dr|z3d
how about zzz, onon_?
dr|z3d
your i2pd pimping failed. sorry.
onon_
Does zzz have a local connection?
dr|z3d
you'd have to ask him, but I don't think he's using a bouncer.
onon_
And I think he does.
dr|z3d
doesn't much matter, though, does it? he's had a persistent connection for 6 days. and your point is?
onon_
user1 uses modified i2pd
dr|z3d
if you're trying to extol the advantages of i2pd, you're not doing a great job.
onon_
=(
onon_
I'll try better next time...
orignal
zzz uses Nazi's server
orignal
that's less loaded that postman's
incognet
Whatever, I give up on the ZNC setup for now. Nothing seems to work to authenticate this user automatically.
orignal
what?
zzz
not local, no bouncer
RN
I guess I should do some znc screenshots
cumlord
pretty sure i've seen stream sessions on simp around 8 days
cumlord
did adjust job runners to 4*threads, tried setting router.buildHandlerThreads/router.peerTestConcurrency to defaults, not having much luck past some amount of hours pass
cumlord
zzzot router previously handled 12 server tunnels on -5, past about 8 hours job lag/message delay gets too high, so i can save those routers from lagging out by stopping all tunnels and waiting to catch up i've learned
cumlord
it seems to find a steady state by only running zzzot and 1 sam tunnel (irc server)
cumlord
trying with reduced buildhandler threads idk, number of running servers from tunnelmanager correlates with congestion
dr|z3d
build handler threads are normally sufficient at default values.
dr|z3d
peer test concurrency, same.
dr|z3d
normally, unless your router is heavily overloaded, building a tunnel shouldn't take more than a few ms.
dr|z3d
if things are still laggy, set maxJopbRunners to 2* available system threads (vCores) max.
dr|z3d
*maxJobRunners
dr|z3d
iirc, canon sets maxJobRunners to 12.