Rhino 2.5.0 :: Rhino Administration and Deployment Guide :: About the SystemInput Limiter Ramp-up

Ramp-up is an optional procedure that gradually increases the rate that the SystemInput limiter allows — from a small value when a node starts, up to the configured maximum.

This allows time for events such as Just-In-Time compilation and cache-loading, before the maximum work rate applies to the node.

Enabling or disabling ramp-up

Below is a summary of what happens depending on whether ramp-up is enabled or disabled.

Enabled Disabled

Enabled	Disabled
First, Rhino sets the `SystemInput` limiter’s maximum allowed rate to `startRate`. Then, every time Rhino processes `eventsPerIncrement` events, with no rejected events, it adds `rateIncrement` to the rate. Rhino counts all events processed, regardless of whether or not they go through the `SystemInput` limiter. Ramp-up finishes when the current rate reaches the `maxRate` value set for the `SystemInput` limiter.	Nothing special happens when the node starts — the maximum rate the SystemInput limiter allows is simply `maxRate`.

First, Rhino sets the SystemInput limiter’s maximum allowed rate to startRate.
Then, every time Rhino processes eventsPerIncrement events, with no rejected events, it adds rateIncrement to the rate. Rhino counts all events processed, regardless of whether or not they go through the SystemInput limiter.
Ramp-up finishes when the current rate reaches the maxRate value set for the SystemInput limiter.

Nothing special happens when the node starts — the maximum rate the SystemInput limiter allows is simply maxRate.

Ramp-up has no effect if the SystemInput limiter’s bypassed flag is true.

You configure ramp-up globally, but each node ramps up independently. So if a node restarts, it ramps up again — without affecting other already running nodes.

Previous page Next page