Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COThanks so much. My mistake was forgetting that I was sending two packets at the same time to that machine, one on port 20600 and one on 20700. So I had confused the two conversations. Now I guess my question is: how can I make the re-transmission faster? Why the long pause between the duplicate ack for an earlier packet and the re-transmission from my end? How can I make this faster?
      singulars
    2. COCan you run a capture on both your PC and the Linux box at the same time? This looks like a classic case of a packet not reaching its destination. I assume this connection is over a LAN with some sort of switch. If that's the case, maybe you have some other tools to monitor overall network congestion. I'm not sure if you can change the retransmit timeout, but in any event that seems to be treating symptoms and not the cause.
      singulars
    3. COActually, I did manage to drastically reduce the number of transmissions today by increasing the ARP cache timeout. I noticed whenever more than 2 minutes elapsed between sends on the socket, the probability of a re-transmit increased dramatically. I looked for anything with a period of 2 minutes and found the ARP cache and increased it and there weren't any issues for the past several hours. But that still leaves two question - 1) Why does increasing the ARP cache timeout fix it? 2) Is there a way to shorten the re-transmit time for those times when it still does happen.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload