Partager via

Burst handling

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Server 8 Beta

Burst handling

WINS servers can now support handling of high-volume (burst) server loads. Bursts occur when a large number of WINS clients actively and simultaneously try to register their local names in WINS, such as when a power failure occurs. When power is later restored, many users start and register their names simultaneously on the network, which creates high levels of WINS traffic. With burst-mode support, a WINS server can respond positively to these client requests, even before it processes and physically enters those updates in the WINS server database.

How burst handling works

Burst mode uses a burst-queue size as a threshold value. This value determines how many name registration and name refresh requests sent by WINS clients are processed normally before burst-mode handling is started. By default, the value is 500. A WINS server initiates burst handling whenever the number of WINS client registration requests exceeds the burst queue size.

In burst handling, additional client requests are immediately answered with a positive response by the WINS server. The response also includes a varied Time-To-Live (TTL) to clients, which helps regulate the client registration load and distribute processing of the requests over time. This slows the refresh and retry rate for new WINS clients and regulates the burst of WINS client traffic.

For example, if the burst queue size is 500 entries and more than 500 requests are active, the WINS server replies immediately to the next 100 WINS client registration requests by sending early success responses with a starting TTL value of 5 minutes. For each additional round of 100 client requests, 5 minutes more are added to the TTL up to a maximum of 50 minutes. If WINS client traffic still arrives at burst levels, the next round of 100 client requests are answered with the initial TTL value of 5 minutes, and the entire process for incrementing the response TTL is repeated.

This behavior continues until the WINS server reaches its maximum intake level of 25,000 name registration and refresh queries. At this point, the WINS server begins dropping queries.

Using the WINS console, you can choose to configure the level of burst handling used by the server which modifies the size of the burst queue to accommodate either a low, medium or large burst situation.

Note

  • Any WINS server running Windows NT Server 4.0 (with Service Pack 3 or later installed), Windows 2000, or Windows Server 2003 can use burst handling.