[Tech] [Old frost] network bandwidth usage and QoS

[Matthew Toseland]

----- ET at mj+bSV4hxRMtCj9fcwy4Ww9_3mc ----- 2007.05.27 - 10:13:11GMT -----

I think Stochastic Fairness Queuing (SFQ) algorithm is appropriate for freenet 
output.

http://www.opalsoft.net/qos/DS-25.htm

- equalize bandwidth between each actif node link
- minimize delay on each link
- adapt link usage when bandwidth change (due to QoS on network or saturate 
network)

----- Anonymous at o9_0DTuZniSf_+oDmRsonByWxsI ----- 2007.05.27 - 
20:08:46GMT -----

Node A and Node B connected:
- Node A has bandwidth 1000 with 15 active connections
- Node B has bandwidth 5000 with 8 active connections

As result, node B feels ok to send to node A datastream with seemingly fair 
speed of 625, but from Node A standpoint the fair level would be 67.

10x difference. So unlikely a particular QoS algorithm will have noticeable 
impact on overall performance/fairness, there are much more critical 
bandwidth control tasks to optimize.

(But it should be easy to check: SFQ among other algorithms is implemented in 
linux, so just configure host, raise fred outgoing bandwidth limit to the sky 
(and make sure fred has something extra to send - like large storage, 
and/and/or large inserts), and try to notice any difference, preferably 
expressed in numbers. I am serious, please report the results if any.)

On the other hand, good QoS could be useful on a host/network with freenet 
node sharing relatively slow internet connection with other 
applications/users. Unfortunatelly for outgoing traffic only.

----- ET at mj+bSV4hxRMtCj9fcwy4Ww9_3mc ----- 2007.05.28 - 07:37:39GMT -----

I use already QoS on my computer, HTB and SFQ for freenet. When freenet's 
bandwidth is reduce by QoS, bwlimitDelayTime and nodeAveragePingTime increase 
and reject requests (SUB_MAX_PING_TIME, MAX_PING_TIME and Output bandwidth 
liability). Problem is long time to take again normal activity, about 30 
minutes after QoS give back bandwidth.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://emu.freenetproject.org/pipermail/tech/attachments/20070808/a01d5b2c/attachment.pgp