This page describes the global configuration items for Liberator’s client-update throttling. Throttling reduces the performance impact of high update rates by merging updates together.
|Throttling merges updates together. For information on sending updates to clients in batches, see Bursting.|
object-throttle-default-level specifies the throttle level that all users start at when they log in to Liberator. This is a zero-based index to the array of throttle times specified in the object-throttle-times array, or in the throttle-times array of add-object.
Before disabling throttling globally, consider if any objects would benefit from some level of update throttling. For instructions on disabling throttling for specific objects and namespaces, see Disabling throttling.
FALSE (throttling is enabled)
Alias for object-throttle-times.
For most scenarios, specifying one time is sufficient (the default is
1.0). When multiple times are specified, clients can select the most appropriate throttle time for their network conditions and use case. This is called 'levelling', and the initial level for clients is set by the global item object-throttle-default-level.
Updates from generic objects are throttled from Liberator 7.1.24. Generic objects do not support 'levelling', and throttled updates from generic objects only use the first value in the
object-throttle-time time … [stopped|paused]
Type: array of floats and strings
Values accepted: floating-point numbers, 0, 'stopped', and 'paused'
The array must be in ascending order of throttle times, and if you use
paused, it must be the last entry in the array. Including
paused allows clients to pause updates from objects.