@eyedeekay
&eche|on
&zzz
+RN
+StormyCloud
+T3s|4
+acetone
+cumlord
+dr|z3d
+eche|off
+not_bob
+orignal
+postman
+qend-irc2p
+snex
Arch2
Birdy
BravoOreo
BubbRubb
Chrono
Daddy_
Dann
Guest99
Irc2PGuest2010
Irc2PGuest20149
Irc2PGuest30832
Irc2PGuest49068
Irc2PGuest63942
Irc2PGuest74254
Irc2PGuest86777
Irc2PGuest88361
Irc2PGuest95708
Onn4l7h
Onn4|7h
Over
Sisyphus
Sleepy
SlippyJoe
T3s|4_
Teeed
Yotsu
aargh2
ac9f
anontor
b3t4f4c3__
dr4wd3
duanin2
duck
eyedeekay_bnc
gelleger1
leopold_
makoto
mareki2p_
matean
n1
nilbog
poriori
profetikla
r00tobo
rapidash
shiver_
solidx66
thetia
u5657
uop23ip
w8rabbit
wodencafe2
x74a6
dr|z3d
zzz: any scope for shunting some of the eventpumper load onto NTCP Finisher threads? they seem underutilized right now.
dr|z3d
NTCP reader threads are being exercised more, writer threads, not so much, and then finisher threads least of all.
zzz
dr|z3d, we just did a big shunting with the ntcp write changes
zzz
there's no need to balance workload across threads
zzz
and jogger would tell you the opposite
dr|z3d
ok, just noticing the finisher threads are less noticeably less utilized than both the reader and writer threads.
dr|z3d
*noticeably less utilized
dr|z3d
if I constrain the pumper thread it's happy to use around 50% of one core under loads of ~1MB/s
zzz
probably a candidate for removal of the finisher threads
zzz
jogger hates all of it
dr|z3d
yeah, jogger's not a huge fan of the "let's throw threads at it approach", understandably, given android.
dr|z3d
android/arm
dr|z3d
more arm than android, but yeah.
zzz
not sure if arm is worse at threads than x86, or if it's just worse at everything
dr|z3d
probably the latter for the most part, given the specs of the usual candidates vs x86 (raspberry pis)
dr|z3d
still, if the finisher threads aren't serving much purpose, sounds like a reasonable idea to eliminate them.
zzz
just takes time to analyze and test, and of course be extra careful not to introduce deadlocks