Forum Discussion
szkwg_89687
Nimbostratus
Nimbostratustcp profile for heavy packet loss
at this moment my ltm is using 'High Speed'. when there are heavy packet loss, the retransmission timeout goes to 32 seconds, and sometimes goes to 64 seconds. And this causes a whole transaction takes more than 4 minutes to finish, which usually just needs 2 seconds.
Wondering if 'Scalable' will be better?
Can the maximum retransmission timeout be set to lower value?
13 Replies
szkwg_89687"Maximum Segment Retransmissions" was kept at 8 times. when keepalive is set to 8 seconds, the times of retransmission seemed to be cut to 3 times (i think so, it is a bit hard to simulate packet drop in lab env ). As the app is web-based, it is not easy to tune the app to send another request. Apologize I did not make the situation more clear. Keepalive is chosen because packet loss could be bidirectional, i.e., data packets and some of its ack, I would like to have keepalive packets flowing to have acknowledge number showing up.
Under normal circumstance, RTT is 40ms, data to transfer is about 160KB. basically it is a packet loss burst, within one window several packets got dropped. Yes, retransmissions are timeout based. at first, i was thinking to use new Reno, but it seems the interval of retransmission still went up to 32 sec or 64sec. As the interval turns to so large, I did not notice/calculate smoothed RTT.
I will learn more about wom-tcp-wan-optimized. tcpdump part, I will try to replace ip and upload.- szkwg_89687how can I upload an attachment?
- szkwg_89687wom-tcp-wan-optimized seems to be very aggressive. it ignores multiple packet loss in a burst. it seems like to be used in a very reliable env for large data, long tcp sessions. is it right?
