GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Paws::GameLift::PriorityConfiguration(3) User Contributed Perl Documentation Paws::GameLift::PriorityConfiguration(3)

Paws::GameLift::PriorityConfiguration

This class represents one of two things:

Arguments in a call to a service

Use the attributes of this class as arguments to methods. You shouldn't make instances of this class. Each attribute should be used as a named argument in the calls that expect this type of object.

As an example, if Att1 is expected to be a Paws::GameLift::PriorityConfiguration object:

  $service_obj->Method(Att1 => { LocationOrder => $value, ..., PriorityOrder => $value  });

Results returned from an API call

Use accessors for each attribute. If Att1 is expected to be an Paws::GameLift::PriorityConfiguration object:

  $result = $service_obj->Method(...);
  $result->Att1->LocationOrder

Custom prioritization settings for use by a game session queue when placing new game sessions with available game servers. When defined, this configuration replaces the default FleetIQ prioritization process, which is as follows:

  • If player latency data is included in a game session request, destinations and locations are prioritized first based on lowest average latency (1), then on lowest hosting cost (2), then on destination list order (3), and finally on location (alphabetical) (4). This approach ensures that the queue's top priority is to place game sessions where average player latency is lowest, and--if latency is the same--where the hosting cost is less, etc.
  • If player latency data is not included, destinations and locations are prioritized first on destination list order (1), and then on location (alphabetical) (2). This approach ensures that the queue's top priority is to place game sessions on the first destination fleet listed. If that fleet has multiple locations, the game session is placed on the first location (when listed alphabetically).

Changing the priority order will affect how game sessions are placed.

Priority configurations are part of a GameSessionQueue.

The prioritization order to use for fleet locations, when the "PriorityOrder" property includes "LOCATION". Locations are identified by AWS Region codes such as "us-west-2". Each location can only be listed once.

The recommended sequence to use when prioritizing where to place new game sessions. Each type can only be listed once.

  • "LATENCY" -- FleetIQ prioritizes locations where the average player latency (provided in each game session request) is lowest.
  • "COST" -- FleetIQ prioritizes destinations with the lowest current hosting costs. Cost is evaluated based on the location, instance type, and fleet type (Spot or On-Demand) for each destination in the queue.
  • "DESTINATION" -- FleetIQ prioritizes based on the order that destinations are listed in the queue configuration.
  • "LOCATION" -- FleetIQ prioritizes based on the provided order of locations, as defined in "LocationOrder".

This class forms part of Paws, describing an object used in Paws::GameLift

The source code is located here: <https://github.com/pplu/aws-sdk-perl>

Please report bugs to: <https://github.com/pplu/aws-sdk-perl/issues>

2022-06-01 perl v5.40.2

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.