Google Inc.

Jon P McAlister

Kevin Gibbs

Ryan C Barrett

Kenneth M Ashcraft

Justin Christopher Haugh

Ryan Brown

Kenneth Ashcraft

In an application execution system having a plurality of application servers, each application server stores a plurality of applications, and has computational resources for executing applications in response to received requests. Each application server also includes instructions for loading a respective application into volatile storage and executing the application in response to a request from a client, and for returning a result. A generic application instance may be cloned, creating a pool of generic application instance clones that can be loaded with code for a requested application to produce an application instance. The application instance can then be stored in a cache to be used for a future application request.

Application hosting in a distributed application execution system

A method, system, and computer readable medium for managing applications on an application execution system are disclosed. On an application server the number of instances of a first application type that are in a busy state is determined. This determination is performed at each respective time interval in a plurality of time intervals. Then, a first running average for the busy state of the first application type is computed based upon the number of instances of the first application type that are in a busy state, at the application server, at each respective time interval. A removal request is sent when the first running average for the busy state meets a first removal criterion. The removal request is a request to remove the application server from a data structure that specifies which of a plurality of application servers accept service requests for the first application type.

Distributed scheduler

In a distributed application execution system having a plurality of application servers, each application server has volatile and nonvolatile storage as well as computational resources for executing applications as follows. A plurality of applications is stored in non-volatile storage. At least one such application is a primed application which is derived as follows. An unprimed application is executed and an initialization signal is optionally communicated to the unprimed application. A status signal is obtained from the unprimed application. Upon receipt of the status signal, the unprimed application is checkpointed to produce the primed application, and the primed application is stored. A request to execute the primed application is received from a client system. In response to the request, the primed application is loaded from non-volatile storage into volatile storage, and the primed application is executed. The primed application returns a result to the request to the client system.

Systems and methods for serving applications in an application server environment

In an application execution system having a plurality of application servers and an application master in an application execution system, the application master stores a plurality of applications, including a respective application, in a library for distribution among the application servers, adds a first instance of the respective application from the library to a respective application server for execution, and obtains usage information of one or more applications added to the application servers. In accordance with the usage information, the application master performs one of a predefined set of actions that includes: adding a second instance of the respective application to the plurality of application servers; and removing the first instance of the respective application from the respective application server.

In an application execution system having a plurality of application servers, each application server stores a plurality of applications, and has computational resources for executing applications in response to received requests. Each application server also includes instructions for loading a respective application into volatile storage and executing the application in response to a request from a client, and for returning a result. In addition, each application server includes instructions for conditionally terminating execution of the respective application prior to returning the result if the respective application violates any execution restriction. The execution restrictions may include: a response time limit; an average response time limit over multiple executions of the application; a volatile memory usage limit; a restriction on using non-volatile storage of the application server; and a requirement limiting where state information is stored. The execution restrictions in aggregate maintain scalability of the application execution system.

Application server scalability through runtime restrictions enforcement in a distributed application execution system

In an application execution system having a plurality of application servers, each application server includes non-volatile storage for storing a plurality of applications, volatile storage and computational resources for executing applications in response to requests received by the application execution system and for returning results to the requestors. In addition, each application server includes instructions for conditionally terminating execution of the respective application prior to returning the result if the respective application violates any of a plurality of execution restrictions. The execution restrictions in aggregate maintain scalability of the application execution system with respect to at least one or more of the following limits: number of applications that can be executed and number of requests that can be processed per period of time.

In a distributed application execution system having an application master and a plurality of application servers, each application server includes one or more processors and memory storing one or more programs. The one of more programs include instructions for storing in non-volatile storage a plurality of applications distributed to the application server by the application master, for loading into volatile storage and executing a respective application in response to a received request, and for returning a result to the request. In addition, the one of more programs include instructions for conditionally retaining the respective application in volatile storage, for responding to a future request, when criteria, including at least predefined usage level criteria, are met by the respective application, and otherwise removing the respective application from volatile storage upon returning the result to the request.

Growing community of inventors

Millbrae, CA, United States of America

Jon P McAlister