Opened 9 days ago

Last modified 4 days ago

#2506 new enhancement

Time UDP bandwidth retrans precisely

Reported by: jogger Owned by: zzz
Priority: minor Milestone: undecided
Component: router/transport Version: 0.9.40
Keywords: Cc:
Parent Tickets:

Description

While investigating #2505 I found that locked_shouldSend() sets a random retrans time if no b/w.

I have already developed and tested the sliding b/w window in allocateSendingBytes() for #2412. Building on top of that it would be easy to determine the exact point in time when enough b/w is available for the currently blocked transmission. Would make things a bit faster. Operating on random values would be another reason to abandon getNextDelay()

If you agree I would code that.

Subtickets (add)

Change History (2)

comment:1 Changed 5 days ago by zzz

I think we have to decide what to do about #2412 first. It's still open and it didn't get into .40 as we've been busy and haven't addressed your latest comments there yet, unfortunately.

comment:2 Changed 4 days ago by jogger

OK. I also do not like shooting at moving targets. I already started detailed measurements of your and my proposal for #2412 (big difference) and must now redo those after fixing #2505. One result of fixing #2505 is that the case addressed by the OP now strikes multiple times per second which makes solving it really worthwile.

Note: See TracTickets for help on using tickets.