| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
changed terrain send throotle to be by packets in queue, reduced odds of MTU violation on terrain send (still bad). Most UDP protocol implementations may not mind much, but our code still does
|
| |
|
| |
|
|
|
|
|
|
| |
This is controlled via the console command "debug lludp client set process-unacked-sends true [<avatar-first-name> <avatar-last-name>]"
For debug purposes to see if this process for very bad connections is causing general outbound udp processing delays.
Relates to http://opensimulator.org/mantis/view.php?id=7393
|
|
|
|
| |
conference code use a generic JobEngine class rather than 4 slightly different copy/pasted versions.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This allows one to set the requested throttle (which normally comes from the client) as opposed to the max.
|
|
|
|
|
| |
On server, scene-throttle-max becomes max-scene-throttle and likewise max-new-client-throttle
On clients, throttle-max becomes max
|
|
|
|
|
|
| |
client throttle to be set separately from existing clients.
"debug lludp throttles get/set throttle-max" now only gets and sets current max client throttles
|
|
|
|
|
|
| |
to mirror "debug lludp set"
Information is also available in "show server throttles" but that's more for non-debug info rather than attempting to get and set parameters on the fly for debug purposes.
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
printing any information. Also fix max throttle displayed to be properly kbps
|
|
|
|
| |
value is not set rather than 0
|
|
|
|
|
|
| |
setting of default and existing client throttles.
Doesn't yet adjust until clients submit new throttle settings.
|
|
|
|
|
|
| |
consistency (and because I keep typing throttles).
This will still work with "debug lludp throttle" anyway.
|
|
|
|
| |
- throttle buckets are set in bytes, not bits
|
|
|
|
| |
never applies.
|
|
|
|
| |
which case they apply to all users in the lludp server
|
|
|
|
| |
to potentially set the scene max throttle on the fly.
|
|
|
|
|
|
| |
throttles" command rather than "show throttles"
THis allows us to see the rates when no client is connected to the region.
|
|
|
|
|
|
|
| |
about throttles
This is separate from the user-oriented "show throttles" command since one will often only want to know about varying client throttle settings.
Currently displays max scene throttle and adaptive throttles config if set.
|
|
|