Fleet scaling settings
Documentation for Fleet scaling settings
읽는 시간 4분최근 업데이트: 일 년 전
Fleet scaling settings exist in two locations: at the fleet level and the fleet region level. At both these levels, you can specify most scaling setting values. At the fleet region level, in particular, you can:
- Override values specified at the fleet level
- Control the preferred settings for the reactive scaling system
Minimum available servers
The minimum available servers value determines the minimum number of game servers that the reactive scaling system keeps online and available for new players to join. Keeping a buffer of available game servers reduces the likelihood that players have to wait for the reactive scaling system to start up a cloud machine before they can join a game session. The minimum available servers value has the most influence over the reactive scaling system’s scaling decisions. Refer to Available servers buffer. There are no limits on the number of available servers you can have in your fleet unless you specify a Maximum servers value. The higher the minimum available servers value, the faster your fleet or fleet region responds to sudden increases in players. Higher values also incur a higher maintenance cost. Clanforge advises specifying the minimum available servers at the fleet region level because the ideal value depends on the size of the region and the expected maximum rate of allocation requests in the region.Minimum servers
The minimum servers value determines the absolute minimum number game servers that the reactive scaling system keeps in a fleet or fleet region at any time. This value prevents the reactive scaling system from removing excess capacity. It also ensures the reactive scaling system keeps an additional buffer of offline capacity that the reactive scaler can bring online quickly.Minimum standby servers
The minimum standby servers value dictates the number of game servers within a fleet or fleet region that are in an offline state. Game servers in a standby state are distinct from available game servers in that available game servers are online, but standby game servers aren't. Standby game servers serve as a form of warm capacity that Clanforge can use to host game servers in case of a sharp influx in connected users (CCU). This setting is optional.Maximum servers
The maximum servers value is the total maximum number of game server instances that can exist at a time. You can change this value to control costs associated with scaling into the cloud. The maximum number of servers sets an upper limit on the total number of game server instances in your fleet. If you reach the maximum number of servers, your fleet stops scaling.Allocation timeout
The allocation timeout value determines the time the reactive scaling system waits before force-deallocating allocated game servers, even if players are on the server. This value serves as a hard limit on the time an allocation can exist.Allocation spread
The allocation spread value controls how the reactive scaling system spreads allocations across machines in a fleet or fleet region. The value represents the maximum number of machines the reactive scaler spreads allocations across. The reactive scaler uses a random value between one and the specified allocation spread value. Specifying an allocation spread value that's higher than the number of bare metal machines can't result in additional scaling, but might cause the reactive scaling system to keep machines online longer than necessary. Refer to Allocation spread.Time to live (TTL) values
Time to live values, called TTL values for short, are configuration settings specified at the fleet region level that prevent the reactive scaling system from scaling machines up or down too quickly. Without the TTL settings, the reactive scaling system might add or remove machine capacity too quickly, which can cause increased cost and reduced performance. There are TTL settings that control the time that machines exist in states before the reactive scaling system takes action, such as:- The Shutdown TTL, which is the time a machine exists in an unused state before the reactive scaling system shuts it down
- The Delete TTL, which is the time a cloud machine exists in a shutdown state before the reactive scaling system deletes it
- The Disabled delete TTL, which is the time a cloud machine exists in a disabled state before the reactive scaling system shuts it down