Abstract: This disclosure describes techniques for a game-hosting service of a service provider network to dynamically determine a number of processes that are permitted to concurrently execute on an instance based on health values that indicate performances of the processes running on the instance. The game-hosting service may periodically or continuously receive health values from the instance, or multiple instances in a fleet of instances, and determine whether additional processes may be permitted to run, or if less processes may be permitted to run, on the instance based on the performance of the processes that are concurrently running on the instance. In this way, instances may dynamically be permitted to concurrently execute additional processes, or less processes, to help ensure that computing resources are being efficiently utilized, but also while maintaining acceptable performance for processes (e.g., game sessions) that are hosted on the instances.

Abstract: Live migration can be performed for a process executing on an allocated resource for an application session. During a session it might be determined that it is necessary, or would at least be advantageous, to migrate the process to different resource capacity. New capacity such as a new computing instance can be identified, and synchronized with a current instance to reflect current state information. This can include obtaining state data from a serialized file or transaction log, among other such options. The client devices on the session can be caused to connect or direct state data to the new instance, and when ready the new instance can be responsible for the process, such as by taking over as the application server for the session. Once the client devices are utilizing the new instance, the process can be terminated on the old instance and the instance destroyed or reallocated.

Abstract: Techniques for concurrent execution of multiple content item processes, such as video game processes, on a single virtual machine instance are described herein. In some examples, developers may provide an indication of a desired content item process quantity count, which is a quantity of content item processes for concurrent execution of content item sessions on each of one or more virtual machine instances. Also, in some examples, the content item process quantity count may be adjustable such that it may be changed, for example in response to various conditions or events. Also, in some cases, collected performance metric information may be used to make intelligent decisions regarding scaling of content item processes. In some examples, when a content item session stops executing on a healthy content item process, the content item process may remain active and may be reused by executing one or more subsequent content item sessions.

Abstract: Techniques for content deployment, scaling and telemetry are described herein. Once a content item is made accessible for deployment, one or more instances of the content item may be installed as an image on a virtual machine instance. Additional instances of the content item may then be launched on the same virtual machine instance and/or by copying the image onto any number of additional virtual machine instances. One or more instances of a content item may be configurable to execute with multiple simultaneously assigned users sessions. Information associated with content item instances may be collected, such as a number of occupied user sessions, a number of unoccupied user sessions, content item instance duration, memory usage, and the like. This information may, in some cases, be used to match and assign authorized users to appropriate content item instances.

Abstract: Techniques for content deployment, scaling and telemetry are described herein. Once a content item is made accessible for deployment, one or more instances of the content item may be installed as an image on a virtual machine instance. Additional instances of the content item may then be launched on the same virtual machine instance and/or by copying the image onto any number of additional virtual machine instances. One or more instances of a content item may be configurable to execute with multiple simultaneously assigned users sessions. Information associated with content item instances may be collected, such as a number of occupied user sessions, a number of unoccupied user sessions, content item instance duration, memory usage, and the like. This information may, in some cases, be used to match and assign authorized users to appropriate content item instances.

Abstract: Techniques for content deployment, scaling and telemetry are described herein. Once a content item is made accessible for deployment, one or more instances of the content item may be installed as an image on a virtual machine instance. Additional instances of the content item may then be launched on the same virtual machine instance and/or by copying the image onto any number of additional virtual machine instances. One or more instances of a content item may be configurable to execute with multiple simultaneously assigned users sessions. Information associated with content item instances may be collected, such as a number of occupied user sessions, a number of unoccupied user sessions, content item instance duration, memory usage, and the like. This information may, in some cases, be used to match and assign authorized users to appropriate content item instances.

Abstract: Techniques for content deployment, scaling and telemetry are described herein. Once a content item is made accessible for deployment, one or more instances of the content item may be installed as an image on a virtual machine instance. Additional instances of the content item may then be launched on the same virtual machine instance and/or by copying the image onto any number of additional virtual machine instances. One or more instances of a content item may be configurable to execute with multiple simultaneously assigned users sessions. Information associated with content item instances may be collected, such as a number of occupied user sessions, a number of unoccupied user sessions, content item instance duration, memory usage, and the like. This information may, in some cases, be used to match and assign authorized users to appropriate content item instances.