Whether UDP or TCP is used, to have a reliable transfer, packets have to be acknowledged. (In the case of UDP, the application itself must generate the acks since the protocol doesn't.) Thus the same reasoning applies as to the other question you referred to.
Saturating the "up" part of your Internet connection slows downloading because packets coming "down" have to be acknowledged by your computer and those acknowledgements have to go out via the up link. If your computer falls too far behind in acks because the up link is choked with data, the sender will slow down and start retransmitting the unacknowledged packets. This will appear to you as a decrease in download speed.
2actually, udp is connectionless and does not send ack packets. – Rex – 2012-03-29T03:36:59.903
If you're going to transfer files reliably over UDP you'll have to use some kind of acknowledgment. But the questioner is probably using a UDP based torrent tracker while still doing the file transfers with TCP. – Kyle Jones – 2012-03-29T04:43:32.547
3If you are transferring over UDP, it is not reliable (by design) so there is no acknowledgement. Torrent transfer will generally uses TCP (tcp/6881-tcp/6889) which will send ack packets as it is TCP. But your answer is unclear and implies UDP will have reliable transfer and ack's which is strictly a function of TCP and never on UDP. – Rex – 2012-03-29T14:45:11.930
@Rex Can you answer the question descriptive ? – hamed – 2012-03-29T23:40:02.240
@Rex I understand the difference between TCP and UDP, but it doesn't matter here. No matter which protocol is used, there are going to be ack packets, even if they must be generated by the application itself, otherwise you can't have reliable file transfer. And since those packets have to exist, there must be uplink bandwidth available for them or the download will stall. I've edited the answer to indicate that UDP itself doesn't send ack packets. – Kyle Jones – 2012-03-30T00:04:53.403