IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#saltr
/2023/01/15
~dr|z3d
@RN
@RN_
@StormyCloud
@T3s|4_
@eyedeekay
@postman
@zzz
%Liorar
+FreefallHeavens
+Xeha
+acetone
+bak83
+cumlord
+hk
+poriori
+profetikla
+uop23ip
+weko
An0nm0n
Arch
Danny
DeltaOreo
Irc2PGuest21357
Irc2PGuest21881
Irc2PGuest5995
Irc2PGuest94373
Meow
Nausicaa
Onn4l7h
Onn4|7h
Over
Over1
T3s|4
anon2
anu
boonst
enoxa
mareki2pb
not_bob_afk
orignal
plap
shiver_
simprelay
solidx66
u5657
y2kboy23 I think its working as intended. The widgets increasing when there's a spike in load on my host.
dr|z3d it says it returns a value between 0 and 1. is that per core or total.. not entirely sure, but I *think* it may be per core so I'm / cores * 100.
dr|z3d actually, I like. I'm treating 1 as 100% load on all cores right now. so just * 100 to get the percentage.
y2kboy23 I'd agree with that. They reference the "whole system" in their documentation.
dr|z3d ok, well keep an eye on it and let me know if it starts to go weird..
dr|z3d I'm using cpu load and load average (indicated currently in the cpu bar tooltip) to determine when to throttle sub-tasks that may be causing excessive load.
y2kboy23 That's a smart idea, I'll keep an eye on things
dr|z3d load average is also indicated as %, so anything over 100% means your system has waiting tasks. load average is load / cores * 100.
dr|z3d on linux in htop for example 100% would be 4.0 if you had 4 cores, etc.
y2kboy23 Yep. I don't have a lot running on my host so it'll take a lot to bog it down
dr|z3d remember system load is not the same thing as cpu load.
dr|z3d your system can be under light cpu load and yet still be experiencing a system load backlog, often to be seen on single cpu systems running i2p.
dr|z3d *single core.
dr|z3d ok, let's see if we can address the erratic behavior of the cpu load bar by averaging it out over a minute.
dr|z3d ok, I think I prefer the less spikey cpu bar, it functions more like the memory bar now and gives an average readout, not jumping all over the place.
dr|z3d as a bonus, we now have an optional cpu load average graph
dr|z3d ok, y2kboy23, everything now pushed to the master branch.
dr|z3d (if you needed that for your docker image)
dr|z3d > ok, y2kboy23, everything now pushed to the master branch.
dr|z3d > (if you needed that for your docker image)
y2kboy23 dr|z3d just update. Let's see how things look
dr|z3d y2kboy23: don't forget to enable the cpu load graph!
dr|z3d under Router / CpuLoad on /configstats
dr|z3d it'll take a few minutes for the cpu load to register.
dr|z3d (on the bar)
y2kboy23 It was already enabled
dr|z3d the graph?
dr|z3d not the bar, the /graphs graph...
y2kboy23 I like the congestion sidebar. Nice glance to see how things are.
dr|z3d ah, sounds like you manually added that?
dr|z3d if so, a couple of config tweaks:
dr|z3d (in ~/.i2p/router.config)
dr|z3d routerconsole.advanced=true
dr|z3d routerconsole.showPeerTestAvg=true
dr|z3d the second will add a peer test average readout (good/total average) to the congestion section.
dr|z3d the first will enable various advanced UI display options and configs, and allow you to edit the router.config inline on /configadvanced
dr|z3d it also enables the congestion section if you have a default sidebar layout.
dr|z3d (neither require a router restart)
y2kboy23 too late lol
y2kboy23 That advanced part was something I was looking for. I was puzzled why some pages had it and others did not
XANA dr|z3d, you up?
XANA do you know what my cause The connection was reset error on eppsites?
T3s|4 XANA: does the problem persist after restarting i2p?
XANA yup
XANA I mean some websites load fine others reset
T3s|4 hmmh...perhaps a corrupted addressbook?
T3s|4 XANA: that is easy to test/eliminate; `mv ~/.i2p ~/.i2p-borked` then grab and install a new copy of i2p, which will install a clean copy of ~/.i2p once you start it
dr|z3d if you get connection reset, just reload the page.
dr|z3d nothing to do with a corrupt addressbook
dr|z3d probably means the server's timed out the connection. a reload should work.
XANA updated to 2.1.0-1+
dr|z3d y2kboy23: thanks for the patch for the UI help.
dr|z3d also, I've attempted to smooth out the cpu bar. if the minute average stat > 0, then we use that, / 2, and add the current reading / 2 to give us a percentage. otherwise just the current value.
y2kboy23 dr|z3d No problem. I'll test out your changes here shortly
dr|z3d not easy to strike the right balance, the cpu load reported by the jvm isn't always 100% accurate. but at least the bar's a bit more responsive now.
y2kboy23 Looks better being more responsive
dr|z3d yeah, I think so too.
y2kboy23 Missed one on the Help UI page too
y2kboy23 Fast under Peers
dr|z3d ok, thanks, will take a look when I have an updated router available.
dr|z3d ok, got it, thanks.
dr|z3d easy to see on the page, not so easy in the source :)
y2kboy23 One more...last line in Congestion
y2kboy23 definitely harder to see in source
XANA dr|z3d, after update my node is acting wierd
XANA Declining tunnel requests:
XANA High message delay
XANA hmm restarted and I think it gets stable now