Issues.00233 - lordmundi/wikidoctest GitHub Wiki
Summary: dcomm updates to support throttling and performance feedback
Created: 2010–03–31 18:46
Status: Released
Category: Request
From: frankie
Version: 2.0
Released_In: 2.2
Description:
this is a request to get dcomm to allow throttling, a user setting which would force comm to not update above a certain rate.
also, this request is for some capability to query dcomm for some information, such as how many nodes are being transmitted each pass and whether or not more than one pass must be used to accommodate the data.
jeff: 2010–07–22 - This allows for throttling of comm, by calling comm at a specified rate, not at the scene update frequency. This allows comm to back off on the amount of bandwidth it consumes. Note that large bandwidth activites, such as loading a state, can take a very long time when throttling. To deal with this problem, comm throttling has a threshold value. When the number of nodes received in a single pass of comm exceeds the threshold value, throttling is suspended and comm will run at full scene update frequency. When the number of nodes per comm pass falls back below this threshold, throttling is reactivated.
The following Tcl/Tk commands are now available to control/query the throttling operation.
doug.plugin dcomm get_num_nodes_updated : returns number of nodes updated in the last comm call
doug.plugin dcomm get_throttle_status : returns status: active, inactive, suspended
doug.plugin dcomm get_throttle_rate : returns current throttle rate (in seconds)
doug.plugin dcomm get_throttle_threshold : returns current throttling threshold
doug.plugin dcomm throttle_rate : sets the throttling rate (in seconds)
doug.plugin dcomm throttle_threshold : sets the threshold of changes before suspending
doug.plugin dcomm always_enqueue ‹1|yes|0|no› : activates or deactivates forced enqueueing of nodes, even if unchanged