Throttling process (computing): Difference between revisions

Revision as of 11:56, 16 March 2007

Revision as of 05:45, 17 March 2007

Line 1:

AIn software, a throttling [[process (computing)|process]], or a throttling controller as it sometimes called, is responsible for regulating the rate at which application processing is conducted, either fixedly or dynamically.

{{Confusing|March 2007}}

For example, in high [[throughput]] processing scenarios, as may be common in online transactional processing ([[OLTP]]) architectures, a throttling controller may be imbedded in the application hosting platform to balance the application's outbound publishing rates with its inbound consumption rates, optimizingoptimize available system resources for the processing profile, and preventingprevent eventually unsustainable consumption. In, say, an enterprise application integration ([[EAI|enterprise application integration|EAI]]) (EAI) architecture, a throttling process may be built into the application logic to prevent aan expectedly slow end-system from becoming overloaded as a result of overly aggressive publishing from the [[middleware]] publishingtier.

A throttling [[process (computing)|process]], or a throttling controller, is responsible for regulating the rate at which application processing is conducted, either fixedly or dynamically.

For example, in high [[throughput]] processing scenarios, as may be common in [[OLTP]] architectures, a throttling controller may be imbedded in the platform to balance publishing rates with consumption rates, optimizing system resources for processing, and preventing unsustainable consumption. In, say, an [[EAI|integration]] architecture, a throttling process may be built into the application logic to prevent a slow end-system from becoming overloaded as a result of overly aggressive [[middleware]] publishing.

{{compsci-stub}}