# RequestScheduler

engine/Source/Core/RequestScheduler.js 40
The request scheduler is used to track and constrain the number of active requests in order to prioritize incoming requests. The ability to retain control over the number of requests in CesiumJS is important because due to events such as changes in the camera position, a lot of new requests may be generated and a lot of in-flight requests may become redundant. The request scheduler manually constrains the number of requests so that newer requests wait in a shorter queue and don't have to compete for bandwidth with requests that have expired.

### Members

#### static Cesium.RequestScheduler.maximumRequests : number
engine/Source/Core/RequestScheduler.js 56

The maximum number of simultaneous active requests. Un-throttled requests do not observe this limit.

Default Value: `50`

#### static Cesium.RequestScheduler.maximumRequestsPerServer : number
engine/Source/Core/RequestScheduler.js 64

The maximum number of simultaneous active requests per server. Un-throttled requests or servers specifically listed in `requestsByServer` do not observe this limit.

Default Value: `18`

#### static Cesium.RequestScheduler.requestsByServer : object
engine/Source/Core/RequestScheduler.js 80

A per server key list of overrides to use for throttling instead of `maximumRequestsPerServer`. Useful when streaming data from a known HTTP/2 or HTTP/3 server.

##### Examples:

    RequestScheduler.requestsByServer["myserver.com:443"] = 18;

    RequestScheduler.requestsByServer = {
      "api.cesium.com:443": 18,
      "assets.cesium.com:443": 18,
    };

#### static Cesium.RequestScheduler.throttleRequests : boolean
engine/Source/Core/RequestScheduler.js 87

Specifies if the request scheduler should throttle incoming requests, or let the browser queue requests under its control.

Default Value: `true`

Need help? The fastest way to get answers is from the community and team on the Cesium Forum.