sharing same files, > 700 MB, UL limit = 30kB/s, correct UL
bandwidth margin
analysed data : stats and verbose log
Stats :
Runtime : 2d1h54m
UL sessions : 1257
Successfull UL sessions : 1076
Failed UL sessions : 181
Average Uploaded per session : 4.70
MB
Average UL time : 24'12"
Verbose log :
% completed sessions : 44
% IC95%
[39.80-48.11]
(84% total UL)
avgul / completed session : 8.19 MB
Stats :
Runtime : 2d11h14m
UL sessions : 1556
Successfull UL sessions : 1355
Failed UL sessions : 201
Average Uploaded per session : 4.53
MB
Average UL time : 14'40"
Verbose log :
% completed sessions : 38% IC95%
[34.42-41.08]
(85% total UL)
avgul / completed session : 7.25 MB
-
Xtreme 7.2 :
Ul slot limit 5 kB/s
Stats :
Runtime : 2d1h51m
UL limit 30 kB/s
UL sessions : 1757
Successfull UL sessions : 1653
Failed UL sessions : 104
Average Uploaded per session : 3.00
MB
Average UL time : 17'37"
Verbose log:
% completed sessions : 55 % IC95%
[51.63-57.65] (89
% total UL)
avgul / completed session : 4.69 MB (=> specific
"Xtreme full chunk")
-
MorphXT v11.3 :
no PBF, no friend slot, no PS, no slot limit, don't remove spare
trickle
slots
Stats :
Runtime : 2d1h45m
UL sessions : 1734
Successfull UL sessions : 1421
Failed UL sessions : 313
Average Uploaded per session : 3.46
MB
Average UL time : 15'17"
Verbose log :
% completed sessions : 31% IC95%
[28.65-33.05]
(86% total UL)
avgul / completed session : 8.58 MB
Graphic
(with IC 95%)
the numbers are relative (maybe depending on shared
files, didn't assess variance/file, but maybe more on UL limit) but order/behavior may not change.
Why completed Ul sessions ?
because they represente 85 to 90% of total UL meaning remaining
sessions are kind of "wasted UL sessions" mainly used to adjust UL or
simply closed for connection pb. And when you waited 12 h to get a slot
you don't want your slot to be open and closed 50 s later to adjust
UL... globally it creates a part of random queue (whereas basically
it's based on waiting time and credits). Random means 50 % longer...
and 50 % quicker, but usually we always focus on longer DL, that's a
human bias.
-morphXT
few/no trickle slots : opens new slots (mostly quickly close)
to offset an UL drop (yellow bars in graph) => spike then
focus... until a new spike because UL focused on too few slots
Cycle :
spike/focus
result : much more interrupted/failed sessions for morph.
a big spike in verbose :
-Xtreme
seems very steady, a
long and important drop in UL for xtreme doesn't trigger
any burst of UL slots, baseline 10 slots @ 30 kB/s
-ZZUL
a more efficient Ul compared to morphXT : it keeps trickle slot opened longer,
morph
quickly close them => clients "in stand by" have more chance to
complete their session, can prevent from opening too many useless slots, graphically cycle spike/focus is much smoother.
-emule
049.c
baseline 8 slots vs 10 for Xtreme -> some small
"UL
slots burst" i can't see in Xtreme + longer UL session (8.19 vs 4.69
MB), but i bet main difference comes from bursts and not from session
lenght.
