Auteur Sujet: Débit en baisse depuis migration à l'offre 1000/200 (Lu 19159 fois)

unrealdtc · « **Réponse #12 le:** 08 septembre 2014 à 20:29:37 »

Citation de: vivien le 08 septembre 2014 à 19:55:34

Pourrais-tu réaliser un test NDT ? => http://www.measurementlab.net/tools/ndt
Il faudrait copier / coller ce qui est dans "Détails"

J'ai fait le test avec Chrome :

Code: [Sélectionner]

Client System Details
OS data:: Linux, Architecture: x86
Flash Info: Version = LNX 15,0,0,152
The slowest link in the end-to-end path is a
2.4 Gbps OC-48 subnet
Information: Other network traffic is congesting the link
This connection is network limited 92.38% of the time
2.4 Gbps OC-48 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 175.95ms
the Packet size = 1448bytes
16 packets retransmitted
895 duplicate acks received
1032 SACK blocks received
The connection was idle 0.00 seconds (0.00% of the time)
C2S throughput test: Packet queuing detected: 3.87%
S2C throughput test: Packet queuing detected: 3.87%
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgement:
ON
RFC 896 Nagle Algorithm:
ON
RFC 3168 Explicit Congestion Notification:
OFF
RFC 1323 Time Stamping:
ON
RFC 1323 Window Scaling:
ON; Scaling Factors - Server=7, Client=7
The theoretical network limit is 1.21 Mbps
The NDT server has a 713.18 KByte buffer which limits the throughput to 63.33 Mbps
Your PC/Workstation has a 2299.38 KByte buffer which limits the throughput to 102.10 Mbps
The network based flow control limits the throughput to 23.92 Mbps
Client Data reports link is OC-48
Client Acks report link is OC-48
Server Data reports link is OC-48
=== Results sent by the server ===
CurMSS: 1448
X_Rcvbuf: 87380
X_Sndbuf: 1460592
AckPktsOut: 0
BytesRetrans: 23168
CongAvoid: 814
CongestionOverCount: 8
CongestionSignals: 7
CountRTT: 1286
CurCwnd: 20272
CurRTO: 380
CurRwinRcvd: 2354560
CurRwinSent: 5888
CurSsthresh: 15928
DSACKDups: 0
DataBytesIn: 0
DataBytesOut: 3868928
DataPktsIn: 0
DataPktsOut: 2618
DupAcksIn: 895
ECNEnabled: 0
FastRetran: 7
MaxCwnd: 551688
MaxMSS: 1448
MaxRTO: 880
MaxRTT: 253
MaxRwinRcvd: 2354560
MaxRwinSent: 5888
MaxSsthresh: 263536
MinMSS: 1448
MinRTO: 378
MinRTT: 174
MinRwinRcvd: 29312
MinRwinSent: 5792
NagleEnabled: 1
OtherReductions: 6
PktsIn: 2285
PktsOut: 2618
PktsRetrans: 16
RcvWinScale: 7
SACKEnabled: 3
SACKsRcvd: 1032
SendStall: 0
SlowStart: 405
SampleRTT: 175
SmoothedRTT: 177
SndWinScale: 7
SndLimTimeRwin: 0
SndLimTimeCwnd: 9978051
SndLimTimeSender: 823589
SndLimTransRwin: 0
SndLimTransCwnd: 12
SndLimTransSender: 12
SndLimBytesRwin: 0
SndLimBytesCwnd: 3590480
SndLimBytesSender: 278448
SubsequentTimeouts: 0
SumRTT: 226269
Timeouts: 0
TimestampsEnabled: 1
WinScaleRcvd: 7
WinScaleSent: 7
DupAcksOut: 0
StartTimeUsec: 381692
Duration: 10805376
c2sData: 8
c2sAck: 8
s2cData: 8
s2cAck: 10
half_duplex: 0
link: 0
congestion: 1
bad_cable: 0
mismatch: 0
spd: 2.87
bw: 1.21
loss: 0.002673797
avgrtt: 175.95
waitsec: 0.00
timesec: 10.00
order: 0.3917
rwintime: 0.0000
sendtime: 0.0762
cwndtime: 0.9238
rwin: 17.9639
swin: 11.1434
cwin: 4.2090
rttsec: 0.175948
Sndbuf: 1460592
aspd: 0.00000
CWND-Limited: -0.02
minCWNDpeak: 17376
maxCWNDpeak: 531416
CWNDpeaks: 5

J'avoue que c'est un peu du chinois pour moi tout ça O__O

[edit]

J'ai capturé un DL avec "wget -O /dev/null -4 http://ipv4.intuxication.testdebit.info/fichiers/100Mo.dat" qui avait 6,85 Mo/s de débit moyen avec "tcpdump -i enp0s20u1 -w ipv4.intuxication.testdebit.info_1.cap -s9000 host 62.210.156.12"

La capture est ci-dessous : http://media.slashorg.net/ipv4.intuxication.testdebit.info.cap.gz

kgersen · « **Réponse #13 le:** 08 septembre 2014 à 21:19:24 »

Flash 15 beta ? C'est Chrome beta ou dev donc?

Code: [Sélectionner]

Web100 reports the Round trip time = 175.95ms

on dirait que tu vas chercher loin le serveur... y'a pas un VPN actif quelque part ?

il manque le résultat du test pour avoir l'ip du serveur, un truc du genre:

Code: [Sélectionner]

NDT test run towards M-Lab server
ndt.iupui.mlab1.par01.measurement-lab.org

RTT between client and M-Lab server
1 ms

DOWNLOAD SPEED
410.7 Mbps

UPLOAD SPEED
54.5 Mbps

vivien · « **Réponse #14 le:** 08 septembre 2014 à 21:26:16 »

Tu as oublié d'indiquer les données débit / ping.

Voici ce que cela donne avec ma Bbox fibre sur le réseau Numericable :

NDT test run towards M-Lab server ndt.iupui.mlab3.par01.measurement-lab.org
RTT between client and M-Lab server 11 ms
DOWNLOAD SPEED 92.9 Mbps
UPLOAD SPEED 5.0 Mbps

Client System Details
OS data:: Linux, Architecture: x86
Flash Info: Version = LNX 14,0,0,125
The slowest link in the end-to-end path is a 45 Mbps T3/DS3 subnet
Information: Other network traffic is congesting the link
This connection is network limited 97.06% of the time
45 Mbps T3/DS3 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 30.47ms
the Packet size = 1448bytes
181 packets retransmitted
370 duplicate acks received
483 SACK blocks received
The connection was idle 0.00 seconds (0.00% of the time)
C2S throughput test: Packet queuing detected: 2.44%
S2C throughput test: Packet queuing detected: 2.44%
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgement: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: ON
RFC 1323 Window Scaling:ON; Scaling Factors - Server=7, Client=7
The theoretical network limit is 72.81 Mbps
The NDT server has a 869.78 KByte buffer which limits the throughput to 446.08 Mbps
Your PC/Workstation has a 2890.50 KByte buffer which limits the throughput to 741.22 Mbps
The network based flow control limits the throughput to 191.82 Mbps
Client Data reports link is T3;
Client Acks report link is Ethernet
Server Data reports link is OC-48
Server Acks report link is OC-48
=== Results sent by the server ===
CurMSS: 1448
X_Rcvbuf: 87380
X_Sndbuf: 1781304
AckPktsOut: 0
BytesRetrans: 260664
CongAvoid: 35031
CongestionOverCount: 0
CongestionSignals: 2
CountRTT: 36014
CurCwnd: 362000
CurRTO: 230
CurRwinRcvd: 2959872
CurRwinSent: 5888
CurSsthresh: 231680
DSACKDups: 0
DataBytesIn: 0
DataBytesOut: 119327064
DataPktsIn: 0
DataPktsOut: 80631
DupAcksIn: 370
ECNEnabled: 0
FastRetran: 2
MaxCwnd: 765992
MaxMSS: 1448
MaxRTO: 254
MaxRTT: 59
MaxRwinRcvd: 2959872
MaxRwinSent: 5888
MaxSsthresh: 382272
MinMSS: 1448
MinRTO: 212
MinRTT: 11
MinRwinRcvd: 29312
MinRwinSent: 5792
NagleEnabled: 1
OtherReductions: 22
PktsIn: 36383
PktsOut: 80631
PktsRetrans: 181
RcvWinScale: 7
SACKEnabled: 3
SACKsRcvd: 483
SendStall: 0
SlowStart: 761
SampleRTT: 28
SmoothedRTT: 30
SndWinScale: 7
SndLimTimeRwin: 0
SndLimTimeCwnd: 9994077
SndLimTimeSender: 302292
SndLimTransRwin: 0
SndLimTransCwnd: 18
SndLimTransSender: 18
SndLimBytesRwin: 0
SndLimBytesCwnd: 118783376
SndLimBytesSender: 543688
SubsequentTimeouts: 0
SumRTT: 1097196
Timeouts: 0
TimestampsEnabled: 1
WinScaleRcvd: 7
WinScaleSent: 7
DupAcksOut: 0
StartTimeUsec: 596663
Duration: 10298763
c2sData: 4
c2sAck: 3
s2cData: 8
s2cAck: 8
half_duplex: 0
link: 0
congestion: 1
bad_cable: 0
mismatch: 0
spd: 92.71
bw: 72.81
loss: 0.000024804
avgrtt: 30.47
waitsec: 0.00
timesec: 10.00
order: 0.0102
rwintime: 0.0000
sendtime: 0.0294
cwndtime: 0.9706
rwin: 22.5820
swin: 13.5903
cwin: 5.8441
rttsec: 0.030466
Sndbuf: 1781304
aspd: 0.00000
CWND-Limited: -0.05
minCWNDpeak: 149144
maxCWNDpeak: 754408
CWNDpeaks: 2

Pour toi voici les lignes importantes :

16 packets retransmitted
The NDT server has a 713.18 KByte buffer which limits the throughput to 63.33 Mbps
Your PC/Workstation has a 2299.38 KByte buffer which limits the throughput to 102.10 Mbps
The network based flow control limits the throughput to 23.92 Mbps
MaxRTT: 253
MaxRwinRcvd: 2354560
MinMSS: 1448
MinRTO: 378
MinRTT: 174

Très peu de paquets perdus. Ce n'est pas la cause du débit limité.
Rwin de 2,3 Mo (données non acquittées max), cela permet au débit de monter
MSS de 1448, parfait.

La cause semble être le ping. Visiblement le ping min a été de 174 ms !

vivien · « **Réponse #15 le:** 08 septembre 2014 à 21:55:39 »

Pour la capture Wireshark, le ping est de 15ms donc là pas de souci.

Rwin max de 915 Ko c'est bon
MSS de 1460 qui est respecté c'est bon

1077 Paquets perdus, c'est beaucoup trop

Débit de 7160 Ko/s soit 57,3 Mb/s, c'est vraiment pas bon mais je n'arrive pas a expliquer pourquoi.
Le graphe contre que le débit n'a jamais été bon et qu'il n'y a pas eu d'incident important pendant la transmission.

$ tcptrace --nores_addr -lrW ipv4.intuxication.testdebit.info.cap 1 arg remaining, starting with 'ipv4.intuxication.testdebit.info.cap' Ostermann's tcptrace -- version 6.6.7 -- Thu Nov 4, 2004 106326 packets seen, 106326 TCP packets traced elapsed wallclock time: 0:00:00.103495, 1027353 pkts/sec analyzed trace file elapsed time: 0:00:13.966191 TCP connection info: 1 TCP connection traced: TCP connection 1: host a: 192.168.10.100:33337 host b: 62.210.156.12:80 complete conn: yes first packet: Mon Sep 8 20:50:43.226985 2014 last packet: Mon Sep 8 20:50:57.193176 2014 elapsed time: 0:00:13.966191 total packets: 106326 filename: ipv4.intuxication.testdebit.info.cap a->b: b->a: total packets: 37255 total packets: 69071 ack pkts sent: 37254 ack pkts sent: 69071 pure acks sent: 37252 pure acks sent: 1 sack pkts sent: 1948 sack pkts sent: 0 dsack pkts sent: 7 dsack pkts sent: 0 max sack blks/ack: 2 max sack blks/ack: 0 unique bytes sent: 148 unique bytes sent: 100000308 actual data pkts: 1 actual data pkts: 69068 actual data bytes: 148 actual data bytes: 100010444 rexmt data pkts: 0 rexmt data pkts: 7 rexmt data bytes: 0 rexmt data bytes: 10136 zwnd probe pkts: 0 zwnd probe pkts: 0 zwnd probe bytes: 0 zwnd probe bytes: 0 outoforder pkts: 0 outoforder pkts: 1077 pushed data pkts: 1 pushed data pkts: 421 SYN/FIN pkts sent: 1/1 SYN/FIN pkts sent: 1/1 req 1323 ws/ts: Y/Y req 1323 ws/ts: Y/Y adv wind scale: 7 adv wind scale: 7 req sack: Y req sack: Y sacks sent: 1948 sacks sent: 0 urgent data pkts: 0 pkts urgent data pkts: 0 pkts urgent data bytes: 0 bytes urgent data bytes: 0 bytes mss requested: 1460 bytes mss requested: 1460 bytes max segm size: 148 bytes max segm size: 1448 bytes min segm size: 148 bytes min segm size: 1428 bytes avg segm size: 147 bytes avg segm size: 1447 bytes max win adv: 915200 bytes max win adv: 15616 bytes min win adv: 29312 bytes min win adv: 15616 bytes zero win adv: 0 times zero win adv: 0 times avg win adv: 874457 bytes avg win adv: 15616 bytes max owin: 149 bytes max owin: 183897 bytes min non-zero owin: 1 bytes min non-zero owin: 1 bytes avg owin: 1 bytes avg owin: 3297 bytes wavg owin: 0 bytes wavg owin: 3614 bytes initial window: 148 bytes initial window: 4344 bytes initial window: 1 pkts initial window: 3 pkts ttl stream length: 148 bytes ttl stream length: 100000308 bytes missed data: 0 bytes missed data: 0 bytes truncated data: 0 bytes truncated data: 0 bytes truncated packets: 0 pkts truncated packets: 0 pkts data xmit time: 0.000 secs data xmit time: 13.919 secs idletime max: 15.8 ms idletime max: 16.1 ms throughput: 11 Bps throughput: 7160170 Bps RTT samples: 3 RTT samples: 36054 RTT min: 15.1 ms RTT min: 0.0 ms RTT max: 15.7 ms RTT max: 15.0 ms RTT avg: 15.4 ms RTT avg: 0.0 ms RTT stdev: 0.3 ms RTT stdev: 0.1 ms RTT from 3WHS: 15.1 ms RTT from 3WHS: 0.1 ms RTT full_sz smpls: 2 RTT full_sz smpls: 2 RTT full_sz min: 15.1 ms RTT full_sz min: 0.1 ms RTT full_sz max: 15.7 ms RTT full_sz max: 0.1 ms RTT full_sz avg: 15.4 ms RTT full_sz avg: 0.1 ms RTT full_sz stdev: 0.0 ms RTT full_sz stdev: 0.0 ms post-loss acks: 0 post-loss acks: 5 segs cum acked: 0 segs cum acked: 33004 duplicate acks: 0 duplicate acks: 1174 triple dupacks: 0 triple dupacks: 13 max # retrans: 0 max # retrans: 0 min retr time: 0.0 ms min retr time: 0.0 ms max retr time: 0.0 ms max retr time: 0.0 ms avg retr time: 0.0 ms avg retr time: 0.0 ms sdv retr time: 0.0 ms sdv retr time: 0.0 ms

vivien · « **Réponse #16 le:** 08 septembre 2014 à 22:00:37 »

Mon hypothèse serait un problème logiciel...

Si c'est le cas, cela serait une première avec Linux (mais j'ai déja eu des souci sous MacOS X)

Tu me ferais un test avec une autre distribution ou sous Windows ? (Une live clé USB me va bien aussi)

Nico · « **Réponse #17 le:** 08 septembre 2014 à 22:22:35 »

Le truc bizarre vivien c'est qu'il n'avait pas ce soucis sur l'offre 300/50 et c'était tout bien stable. Aujourd'hui il n'a plus même 300/50 stables dans les 1000/200.

unrealdtc · « **Réponse #18 le:** 08 septembre 2014 à 22:34:02 »

Mon souci avec le test ndt est qu'il avait du mal à me géolocaliser correctement, donc il prenait le mauvais serveur. J'ai changé mes settings DNS pour arranger ce problème :

Code: [Sélectionner]

NDT test run towards M-Lab server
ndt.iupui.mlab1.trn01.measurement-lab.org

RTT between client and M-Lab server
29 ms

DOWNLOAD SPEED
169.6 Mbps

UPLOAD SPEED
22.4 Mbps


Client System Details
OS data:: Linux, Architecture: x86
Flash Info: Version = LNX 15,0,0,152
The slowest link in the end-to-end path is a
a 622 Mbps OC-12 subnet
Information: Other network traffic is congesting the link
This connection is network limited 96.23% of the time
622 Mbps OC-12 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 30.32ms
the Packet size = 1448bytes
87 packets retransmitted
3072 duplicate acks received
3279 SACK blocks received
The connection was idle 0.00 seconds (0.00% of the time)
C2S throughput test: Packet queuing detected: 1.74%
S2C throughput test: Packet queuing detected: 1.74%
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgement:
ON
RFC 896 Nagle Algorithm:
ON
RFC 3168 Explicit Congestion Notification:
OFF
RFC 1323 Time Stamping:
ON
RFC 1323 Window Scaling:
ON; Scaling Factors - Server=7, Client=7
The theoretical network limit is 70.26 Mbps
The NDT server has a 2048.00 KByte buffer which limits the throughput to 1055.34 Mbps
Your PC/Workstation has a 3072.00 KByte buffer which limits the throughput to 791.50 Mbps
The network based flow control limits the throughput to 638.68 Mbps
Client Data reports link is OC-12
Client Acks report link is T3;
Server Data reports link is OC-48
Server Acks report link is OC-48
=== Results sent by the server ===
CurMSS: 1448
X_Rcvbuf: 87380
X_Sndbuf: 4194304
AckPktsOut: 0
BytesRetrans: 125976
CongAvoid: 25774
CongestionOverCount: 17
CongestionSignals: 4
CountRTT: 28795
CurCwnd: 356208
CurRTO: 229
CurRwinRcvd: 3145728
CurRwinSent: 5888
CurSsthresh: 343176
DSACKDups: 0
DataBytesIn: 0
DataBytesOut: 220166480
DataPktsIn: 0
DataPktsOut: 148767
DupAcksIn: 3072
ECNEnabled: 0
FastRetran: 4
MaxCwnd: 2538344
MaxMSS: 1448
MaxRTO: 237
MaxRTT: 59
MaxRwinRcvd: 3145728
MaxRwinSent: 5888
MaxSsthresh: 1243832
MinMSS: 1448
MinRTO: 229
MinRTT: 29
MinRwinRcvd: 29312
MinRwinSent: 5792
NagleEnabled: 1
OtherReductions: 26
PktsIn: 31868
PktsOut: 148767
PktsRetrans: 87
RcvWinScale: 7
SACKEnabled: 3
SACKsRcvd: 3279
SendStall: 0
SlowStart: 2701
SampleRTT: 29
SmoothedRTT: 29
SndWinScale: 7
SndLimTimeRwin: 0
SndLimTimeCwnd: 10008008
SndLimTimeSender: 392506
SndLimTransRwin: 0
SndLimTransCwnd: 21
SndLimTransSender: 21
SndLimBytesRwin: 0
SndLimBytesCwnd: 219362640
SndLimBytesSender: 803840
SubsequentTimeouts: 0
SumRTT: 873112
Timeouts: 0
TimestampsEnabled: 1
WinScaleRcvd: 7
WinScaleSent: 7
DupAcksOut: 0
StartTimeUsec: 882216
Duration: 10401630
c2sData: 6
c2sAck: 4
s2cData: 8
s2cAck: 8
half_duplex: 0
link: 0
congestion: 1
bad_cable: 0
mismatch: 0
spd: 169.35
bw: 70.26
loss: 0.000026888
avgrtt: 30.32
waitsec: 0.00
timesec: 10.00
order: 0.0964
rwintime: 0.0000
sendtime: 0.0377
cwndtime: 0.9623
rwin: 24.0000
swin: 32.0000
cwin: 19.3660
rttsec: 0.030322
Sndbuf: 4194304
aspd: 0.00000
CWND-Limited: -0.41
minCWNDpeak: 26064
maxCWNDpeak: 2528208
CWNDpeaks: 4

Sinon, Nico a raison : je n'avais pas de soucis de débit avant mon passage en 1000/200

Et par ailleurs :
- Généralement je fais mes tests de débit depuis un serveur FreeBSD 10 qui est dans la cave, le laptop sous Linux ne fait que confirmer ce que je constate ailleurs
- Avec la nuit qui arrive, mes débits vont remonter progressivement...

Cela dit, je peux te faire une capture sous FreeBSD si cela t’intéresse

[edit]

Capture avec FreeBSD 10 x64 lors d'un DL à vitesse moyenne 6.42Mo/s : http://media.slashorg.net/ipv4.intuxication.testdebit.info_freebsd10.cap.gz

Commande utilisée : tcpdump -i vtnet0 -w ipv4.intuxication.testdebit.info_freebsd10.cap -s9000 host 62.210.156.12

vivien · « **Réponse #19 le:** 08 septembre 2014 à 23:15:47 »

Là il y a une perte importante a la fin du slow start mais sinon rien de spécial.

Je ne comprends pas..

$ tcptrace --nores_addr -lrW ipv4.intuxication.testdebit.info_freebsd10.cap 1 arg remaining, starting with 'ipv4.intuxication.testdebit.info_freebsd10.cap' Ostermann's tcptrace -- version 6.6.7 -- Thu Nov 4, 2004 104201 packets seen, 104201 TCP packets traced elapsed wallclock time: 0:00:00.100625, 1035537 pkts/sec analyzed trace file elapsed time: 0:00:14.916752 TCP connection info: 1 TCP connection traced: TCP connection 1: host a: 192.168.203.10:14058 host b: 62.210.156.12:80 complete conn: yes first packet: Mon Sep 8 22:38:35.121740 2014 last packet: Mon Sep 8 22:38:50.038492 2014 elapsed time: 0:00:14.916752 total packets: 104201 filename: ipv4.intuxication.testdebit.info_freebsd10.cap a->b: b->a: total packets: 35137 total packets: 69064 ack pkts sent: 35136 ack pkts sent: 69064 pure acks sent: 35134 pure acks sent: 1 sack pkts sent: 923 sack pkts sent: 0 dsack pkts sent: 0 dsack pkts sent: 0 max sack blks/ack: 1 max sack blks/ack: 0 unique bytes sent: 150 unique bytes sent: 100000308 actual data pkts: 1 actual data pkts: 69061 actual data bytes: 150 actual data bytes: 100000308 rexmt data pkts: 0 rexmt data pkts: 0 rexmt data bytes: 0 rexmt data bytes: 0 zwnd probe pkts: 0 zwnd probe pkts: 0 zwnd probe bytes: 0 zwnd probe bytes: 0 outoforder pkts: 0 outoforder pkts: 59 pushed data pkts: 1 pushed data pkts: 231 SYN/FIN pkts sent: 1/1 SYN/FIN pkts sent: 1/1 req 1323 ws/ts: Y/Y req 1323 ws/ts: Y/Y adv wind scale: 7 adv wind scale: 7 req sack: Y req sack: Y sacks sent: 923 sacks sent: 0 urgent data pkts: 0 pkts urgent data pkts: 0 pkts urgent data bytes: 0 bytes urgent data bytes: 0 bytes mss requested: 1460 bytes mss requested: 1460 bytes max segm size: 150 bytes max segm size: 1448 bytes min segm size: 150 bytes min segm size: 1428 bytes avg segm size: 149 bytes avg segm size: 1447 bytes max win adv: 427008 bytes max win adv: 15616 bytes min win adv: 24960 bytes min win adv: 15616 bytes zero win adv: 0 times zero win adv: 0 times avg win adv: 380152 bytes avg win adv: 15616 bytes max owin: 151 bytes max owin: 218649 bytes min non-zero owin: 1 bytes min non-zero owin: 1 bytes avg owin: 1 bytes avg owin: 3449 bytes wavg owin: 0 bytes wavg owin: 2797 bytes initial window: 150 bytes initial window: 2896 bytes initial window: 1 pkts initial window: 2 pkts ttl stream length: 150 bytes ttl stream length: 100000308 bytes missed data: 0 bytes missed data: 0 bytes truncated data: 0 bytes truncated data: 0 bytes truncated packets: 0 pkts truncated packets: 0 pkts data xmit time: 0.000 secs data xmit time: 14.867 secs idletime max: 58.2 ms idletime max: 58.1 ms throughput: 10 Bps throughput: 6703893 Bps RTT samples: 3 RTT samples: 34150 RTT min: 15.8 ms RTT min: 0.0 ms RTT max: 16.4 ms RTT max: 9.0 ms RTT avg: 16.1 ms RTT avg: 0.0 ms RTT stdev: 0.3 ms RTT stdev: 0.1 ms RTT from 3WHS: 16.4 ms RTT from 3WHS: 0.0 ms RTT full_sz smpls: 2 RTT full_sz smpls: 2 RTT full_sz min: 16.2 ms RTT full_sz min: 0.0 ms RTT full_sz max: 16.4 ms RTT full_sz max: 0.0 ms RTT full_sz avg: 16.3 ms RTT full_sz avg: 0.0 ms RTT full_sz stdev: 0.0 ms RTT full_sz stdev: 0.0 ms post-loss acks: 0 post-loss acks: 7 segs cum acked: 0 segs cum acked: 34906 duplicate acks: 0 duplicate acks: 860 triple dupacks: 0 triple dupacks: 10 max # retrans: 0 max # retrans: 0 min retr time: 0.0 ms min retr time: 0.0 ms max retr time: 0.0 ms max retr time: 0.0 ms avg retr time: 0.0 ms avg retr time: 0.0 ms sdv retr time: 0.0 ms sdv retr time: 0.0 ms

Paul · « **Réponse #20 le:** 08 septembre 2014 à 23:17:56 »

L'outil NDT fait un peu le yoyo d'un résultat à l'autre pour moi

vivien · « **Réponse #21 le:** 08 septembre 2014 à 23:25:02 »

Bon désolé, cela fait 4 ans que je n'avais pas utilisé TCP Trace.

Dans la première capture, on a 1077 Paquets perdus, c'est beaucoup trop. SUffisant pour expliquer le mauvais débit ?

Dans la seconde on en a uniquement 59, c'est correct et le débit n'est pas meilleur.

unrealdtc · « **Réponse #22 le:** 09 septembre 2014 à 00:27:59 »

Ce qui nous amène à la question "Mais pourquoi ils dropent des paquets en TCP ?" S'agit-il d'une panne ou bien est-ce volontaire ?

J'ai un peu joué avec des tunnels entre mon laptop et une dedibox et je constate, par exemple, qu'un upload TCP marche bien mieux à l'intérieur d'un tunnel OpenVPN UDP :

Code: [Sélectionner]

[  3] local 10.11.12.10 port 46050 connected with 10.11.12.1 port 5001
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0- 1.0 sec  18.2 MBytes   153 Mbits/sec
[  3]  1.0- 2.0 sec  22.4 MBytes   188 Mbits/sec
[  3]  2.0- 3.0 sec  21.2 MBytes   178 Mbits/sec
[  3]  3.0- 4.0 sec  22.6 MBytes   190 Mbits/sec
[  3]  4.0- 5.0 sec  23.8 MBytes   199 Mbits/sec
[  3]  5.0- 6.0 sec  23.8 MBytes   199 Mbits/sec
[  3]  6.0- 7.0 sec  15.5 MBytes   130 Mbits/sec
[  3]  7.0- 8.0 sec  13.0 MBytes   109 Mbits/sec
[  3]  8.0- 9.0 sec  14.4 MBytes   121 Mbits/sec
[  3]  9.0-10.0 sec  15.5 MBytes   130 Mbits/sec
[  3] 10.0-11.0 sec  16.6 MBytes   139 Mbits/sec
[  3] 11.0-12.0 sec  16.8 MBytes   141 Mbits/sec
[  3] 12.0-13.0 sec  19.0 MBytes   159 Mbits/sec
[  3] 13.0-14.0 sec  19.0 MBytes   159 Mbits/sec
[  3] 14.0-15.0 sec  21.4 MBytes   179 Mbits/sec
[  3] 15.0-16.0 sec  21.4 MBytes   179 Mbits/sec
[  3] 16.0-17.0 sec  22.6 MBytes   190 Mbits/sec
[  3] 17.0-18.0 sec  23.8 MBytes   199 Mbits/sec
[  3] 18.0-19.0 sec  20.4 MBytes   171 Mbits/sec
[  3] 19.0-20.0 sec  15.5 MBytes   130 Mbits/sec
[  3] 20.0-21.0 sec  15.6 MBytes   131 Mbits/sec
[  3] 21.0-22.0 sec  17.8 MBytes   149 Mbits/sec
[  3] 22.0-23.0 sec  17.9 MBytes   150 Mbits/sec
[  3] 23.0-24.0 sec  17.9 MBytes   150 Mbits/sec
[  3] 24.0-25.0 sec  20.1 MBytes   169 Mbits/sec
[  3] 25.0-26.0 sec  21.5 MBytes   180 Mbits/sec
[  3] 26.0-27.0 sec  21.2 MBytes   178 Mbits/sec
[  3] 27.0-28.0 sec  23.6 MBytes   198 Mbits/sec
[  3] 28.0-29.0 sec  23.8 MBytes   199 Mbits/sec
[  3] 29.0-30.0 sec  20.4 MBytes   171 Mbits/sec
[  3]  0.0-30.1 sec   587 MBytes   164 Mbits/sec

[Edit]

Et encore quelques tests d'upload TCP iperf réalisés ce matin vers 8h20.

Natif (sans VPN) :

[ 3] local 192.168.10.100 port 45420 connected with 195.154.xx port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 19.9 MBytes 167 Mbits/sec
[ 3] 1.0- 2.0 sec 9.88 MBytes 82.8 Mbits/sec
[ 3] 2.0- 3.0 sec 4.12 MBytes 34.6 Mbits/sec
[ 3] 3.0- 4.0 sec 3.12 MBytes 26.2 Mbits/sec
[ 3] 4.0- 5.0 sec 3.12 MBytes 26.2 Mbits/sec
[ 3] 5.0- 6.0 sec 3.62 MBytes 30.4 Mbits/sec
[ 3] 6.0- 7.0 sec 3.62 MBytes 30.4 Mbits/sec
[ 3] 7.0- 8.0 sec 4.38 MBytes 36.7 Mbits/sec
[ 3] 8.0- 9.0 sec 4.50 MBytes 37.7 Mbits/sec
[ 3] 9.0-10.0 sec 4.12 MBytes 34.6 Mbits/sec
[ 3] 0.0-10.0 sec 60.5 MBytes 50.7 Mbits/sec

Transporté sur un tunnel UDP (OpenVPN) :

[ 3] local 10.11.12.10 port 46139 connected with 10.11.12.1 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 17.0 MBytes 143 Mbits/sec
[ 3] 1.0- 2.0 sec 18.0 MBytes 151 Mbits/sec
[ 3] 2.0- 3.0 sec 14.8 MBytes 124 Mbits/sec
[ 3] 3.0- 4.0 sec 16.0 MBytes 134 Mbits/sec
[ 3] 4.0- 5.0 sec 16.1 MBytes 135 Mbits/sec
[ 3] 5.0- 6.0 sec 17.1 MBytes 144 Mbits/sec
[ 3] 6.0- 7.0 sec 17.2 MBytes 145 Mbits/sec
[ 3] 7.0- 8.0 sec 16.1 MBytes 135 Mbits/sec
[ 3] 8.0- 9.0 sec 16.0 MBytes 134 Mbits/sec
[ 3] 9.0-10.0 sec 16.1 MBytes 135 Mbits/sec
[ 3] 0.0-10.0 sec 165 MBytes 138 Mbits/sec

vivien · « **Réponse #23 le:** 09 septembre 2014 à 08:40:39 »

Tu pourrais faire un test sans la box, en te connectant directement à l'ONT ?

Je suppose que la box a un peu de mal a gérer la 1Gb/s.