| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
them in the code for later use rather than just reverting them.
Fixed the throttle tests for the new algorithm used when packets
are marked as expired.
|
| |
|
|
| |
compute the expected values without depending on the token bucket code.
|
| |
|
|
|
|
|
| |
adaptive throttle by a full MTU. This is consistent with some implementations
of congestion control algorithms and certainly has the effect of opening
the throttle window more quickly after errors. This is especially important
after initial scene load when the number and size of packets is small.
|
| |
|
|
| |
Extends regression tests to test response of adaptive throttles to ack'ed and expired packets.
|
| |
|
|
|
|
|
| |
client throttles properly.
In "show throttles", also renames 'total' column to 'actual' to reflect that it is not necessarily the throttles requested for/by the client.
Also fills out 'target' in non-adapative mode to the actual throttle requested for/by the client.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
settings.
As part of this also refactors code to put all throttle asserts in a single regression test method
|
| |
|
|
|
|
|
|
|
|
| |
throttles would cause client throttles to be lower than expected when total requests exceeded the scene limit.
This was because specifying a max client throttle would always request the max from the parent server throttle, no matter the actual total requests on the client throttle.
This would lead to a lower server multiplier than expected.
This change also adds a 'target' column to the "show throttles" output that shows the target rate (as set by client) if adaptive throttles is active.
This commit also re-adds the functionality lost in recent 5c1a1458 to set a max client throttle when adaptive is active.
This commit also adds TestClientThrottlePerClientAndRegionLimited and TestClientThrottleAdaptiveNoLimit regression tests
|
| |
|
|
| |
Renames to TestSingleClientThrottleRegionLimited()
|
| |
|
|
| |
behaviour of throttles where a region-wide total outbound limit is in place.
|
| | |
|
| |
|
|
| |
a max client total limit is enforced server-side
|
| | |
|
| |
|
