The disclosure of the above-referenced application is hereby incorporated by reference in its entirety.
Generally described, computing devices utilize a communication network, or a series of communication networks, to exchange data. Companies and organizations operate computer networks that interconnect a number of computing devices to support operations or provide services to third parties. The computing systems can be located in a single geographic location or located in multiple, distinct geographic locations (e.g., interconnected via private or public communication networks). Specifically, data centers or data processing centers, herein generally referred to as a “data center,” may include a number of interconnected computing systems to provide computing resources to users of the data center. The data centers may be private data centers operated on behalf of an organization or public data centers operated on behalf, or for the benefit of, the general public.
To facilitate increased utilization of data center resources, virtualization technologies may allow a single physical computing device to host one or more instances of virtual machines that appear and operate as independent computing devices to users of a data center. With virtualization, the single physical computing device can create, maintain, delete, or otherwise manage virtual machines in a dynamic manner. In turn, users can request computer resources from a data center, including single computing devices or a configuration of networked computing devices, and be provided with varying numbers of virtual machine resources.
In some scenarios, virtual machine instances may be configured according to a number of virtual machine instance types to provide specific functionality. For example, various computing devices may be associated with different combinations of operating systems or operating system configurations, virtualized hardware resources and software applications to enable a computing device to provide different desired functionalities, or to provide similar functionalities more efficiently. These virtual machine instance type configurations are often contained within a device image, which includes static data containing the software (e.g., the OS and applications together with their configuration and data files, etc.) that the virtual machine will run once started. The device image is typically stored on the disk used to create or initialize the instance. Thus, a computing device may process the device image in order to implement the desired software configuration.
The foregoing aspects and many of the attendant advantages of this disclosure will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Companies and organizations no longer need to acquire and manage their own data centers in order to perform computing operations (e.g., execute code, including threads, programs, functions, software, routines, subroutines, processes, etc.). With the advent of cloud computing, storage space and compute power traditionally provided by hardware computing devices can now be obtained and configured in minutes over the Internet. Thus, developers can quickly purchase a desired amount of computing resources without having to worry about acquiring physical machines. Such computing resources are typically purchased in the form of virtual computing resources, or virtual machine instances. These instances of virtual machines are software implementations of physical machines (e.g., computers), which are hosted on physical computing devices, and may contain operating systems and applications that are traditionally provided on physical machines. These virtual machine instances are configured with a set of computing resources (e.g., memory, CPU, disk, network, etc.) that applications running on the virtual machine instances may request and can be utilized in the same manner as physical computers.
However, even when virtual computing resources are purchased, developers still have to decide how many and what type of virtual machine instances to purchase, and how long to keep them. For example, the costs of using the virtual machine instances may vary depending on the type and the number of hours they are rented. In addition, the minimum time a virtual machine may be rented is typically on the order of hours. Further, developers have to specify the hardware and software resources (e.g., type of operating systems and language runtimes, etc.) to install on the virtual machines. Other concerns that they might have include over-utilization (e.g., acquiring too little computing resources and suffering performance issues), under-utilization (e.g., acquiring more computing resources than necessary to run the codes, and thus overpaying), prediction of change in traffic (e.g., so that they know when to scale up or down), and instance and language runtime startup delay, which can take 3-10 minutes, or longer, even though users may desire computing capacity on the order of seconds or even milliseconds.
In some cases, there may be virtual compute systems that acquire and manage such virtual computing resources and provide compute capacity to users on a per-request basis. However, depending on the needs of such users, the amount and the timing of the workload received by the virtual compute systems can be unpredictable. The unpredictability may require the virtual compute systems to maintain a large amount of compute capacity (which can be expensive) that is never fully utilized just to be able to handle the worst case scenarios (e.g., a large amount of requests coming in at one time). If the virtual compute systems do not maintain enough capacity on hand to be able to handle a large number of simultaneous requests, the users may experience increased delays, increased error rates, or other performance-related issues. Thus, an improved method of reducing the amount of idle capacity that needs to be maintained is desired.
According to aspects of the present disclosure, by maintaining a pool of pre-initialized virtual machine instances that are ready for use as soon as a user request is received, and automatically managing the amount of capacity available in the pool to service incoming requests, delay (sometimes referred to as latency) associated with executing the user code (e.g., instance and language runtime startup time) can be significantly reduced, and utilization can be improved.
Generally described, aspects of the present disclosure relate to the management of virtual machine instances and containers created therein. Specifically, systems and methods are disclosed which facilitate management of virtual machine instances in a virtual compute system. The virtual compute system maintains a pool of virtual machine instances that have one or more software components (e.g., operating systems, language runtimes, libraries, etc.) loaded thereon. Maintaining the pool of virtual machine instances may involve creating a new instance, acquiring a new instance from an external instance provisioning service, destroying an instance, assigning/reassigning an instance to a user, modifying an instance (e.g., containers or resources therein), etc. The virtual machine instances in the pool can be designated to service user requests to execute program codes. In the present disclosure, the phrases “program code,” “user code,” and “cloud function” may sometimes be interchangeably used. The program codes can be executed in isolated containers that are created on the virtual machine instances. Since the virtual machine instances in the pool have already been booted and loaded with particular operating systems and language runtimes by the time the requests are received, the delay associated with finding compute capacity that can handle the requests (e.g., by executing the user code in one or more containers created on the virtual machine instances) is significantly reduced.
In another aspect, a virtual compute system may monitor incoming requests to execute user code on the virtual compute system, and identify a trend in the requests (e.g., the timing of the requests, the volume of the requests, the periodicity of the requests, etc.). In view of the identified trend, the virtual compute system may anticipate certain code execution requests. Also, the virtual compute system may allow the users to specify a more flexible time frame at which they wish to run their code, such that the virtual compute system may spread out the code executions and reduce the amount of burst capacity that the virtual compute system is anticipated to be able to handle. The compute capacity maintained by the virtual compute system may include a warming pool of virtual machine instances having one or more software components loaded thereon and waiting to be used for handling an incoming request, and an active pool of virtual machine instances that are currently being used to handle one or more requests.
Knowing (or anticipating) when new code execution requests will be received, the virtual compute system can bypass the warming pool or reduce the idle capacity in the warming pool. In addition, the virtual compute system can lower the user's perceived latency by having a virtual machine instance pre-configured and ready to execute the user function when (or shortly before) the request to execute the user function is received. Further, the virtual compute system can achieve improved fleet-level management and load balancing by having knowledge of the number/size of virtual machine instances and/or containers and the duration for which they are going to be used/needed.
Specific embodiments and example applications of the present disclosure will now be described with reference to the drawings. These embodiments and example applications are intended to illustrate, and not limit, the present disclosure.
Illustrative Environment Including Virtual Compute System
With reference to
By way of illustration, various example user computing devices 102 are shown in communication with the virtual compute system 110, including a desktop computer, laptop, and a mobile phone. In general, the user computing devices 102 can be any computing device such as a desktop, laptop, mobile phone (or smartphone), tablet, kiosk, wireless device, and other electronic devices. In addition, the user computing devices 102 may include web services running on the same or different data centers, where, for example, different web services may programmatically communicate with each other to perform one or more techniques described herein. Further, the user computing devices 102 may include Internet of Things (IoT) devices such as Internet appliances and connected devices. The virtual compute system 110 may provide the user computing devices 102 with one or more user interfaces, command-line interfaces (CLI), application programming interfaces (API), and/or other programmatic interfaces for generating and uploading user codes, invoking the user codes (e.g., submitting a request to execute the user codes on the virtual compute system 110), scheduling event-based jobs or timed jobs, tracking the user codes, and/or viewing other logging or monitoring information related to their requests and/or user codes. Although one or more embodiments may be described herein as using a user interface, it should be appreciated that such embodiments may, additionally or alternatively, use any CLIs, APIs, or other programmatic interfaces.
The user computing devices 102 access the virtual compute system 110 over a network 104. The network 104 may be any wired network, wireless network, or combination thereof. In addition, the network 104 may be a personal area network, local area network, wide area network, over-the-air broadcast network (e.g., for radio or television), cable network, satellite network, cellular telephone network, or combination thereof. For example, the network 104 may be a publicly accessible network of linked networks, possibly operated by various distinct parties, such as the Internet. In some embodiments, the network 104 may be a private or semi-private network, such as a corporate or university intranet. The network 104 may include one or more wireless networks, such as a Global System for Mobile Communications (GSM) network, a Code Division Multiple Access (CDMA) network, a Long Term Evolution (LTE) network, or any other type of wireless network. The network 104 can use protocols and components for communicating via the Internet or any of the other aforementioned types of networks. For example, the protocols used by the network 104 may include Hypertext Transfer Protocol (HTTP), HTTP Secure (HTTPS), Message Queue Telemetry Transport (MQTT), Constrained Application Protocol (CoAP), and the like. Protocols and components for communicating via the Internet or any of the other aforementioned types of communication networks are well known to those skilled in the art and, thus, are not described in more detail herein.
The virtual compute system 110 is depicted in
Further, the virtual compute system 110 may be implemented in hardware and/or software and may, for instance, include one or more physical or virtual servers implemented on physical computer hardware configured to execute computer executable instructions for performing various features that will be described herein. The one or more servers may be geographically dispersed or geographically co-located, for instance, in one or more data centers.
In the environment illustrated
In the example of
Users may use the virtual compute system 110 to execute user code thereon. For example, a user may wish to run a piece of code in connection with a web or mobile application that the user has developed. One way of running the code would be to acquire virtual machine instances from service providers who provide infrastructure as a service, configure the virtual machine instances to suit the user's needs, and use the configured virtual machine instances to run the code. Alternatively, the user may send a code execution request to the virtual compute system 110. The virtual compute system 110 can handle the acquisition and configuration of compute capacity (e.g., containers, instances, etc., which are described in greater detail below) based on the code execution request, and execute the code using the compute capacity. The virtual compute system 110 may automatically scale up and down based on the volume, thereby relieving the user from the burden of having to worry about over-utilization (e.g., acquiring too little computing resources and suffering performance issues) or under-utilization (e.g., acquiring more computing resources than necessary to run the codes, and thus overpaying).
Frontend
The frontend 120 processes all the requests to execute user code on the virtual compute system 110. In one embodiment, the frontend 120 serves as a front door to all the other services provided by the virtual compute system 110. The frontend 120 processes the requests and makes sure that the requests are properly authorized. For example, the frontend 120 may determine whether the user associated with the request is authorized to access the user code specified in the request.
The user code as used herein may refer to any program code (e.g., a program, routine, subroutine, thread, etc.) written in a specific program language. In the present disclosure, the terms “code,” “user code,” and “program code,” may be used interchangeably. Such user code may be executed to achieve a specific task, for example, in connection with a particular web application or mobile application developed by the user. For example, the user codes may be written in JavaScript (node.js), Java, Python, and/or Ruby. The request may include the user code (or the location thereof) and one or more arguments to be used for executing the user code. For example, the user may provide the user code along with the request to execute the user code. In another example, the request may identify a previously uploaded program code (e.g., using the API for uploading the code) by its name or its unique ID. In yet another example, the code may be included in the request as well as uploaded in a separate location (e.g., the storage service 108 or a storage system internal to the virtual compute system 110) prior to the request is received by the virtual compute system 110. The virtual compute system 110 may vary its code execution strategy based on where the code is available at the time the request is processed.
The frontend 120 may receive the request to execute such user codes in response to Hypertext Transfer Protocol Secure (HTTPS) requests from a user. Also, any information (e.g., headers and parameters) included in the HTTPS request may also be processed and utilized when executing the user code. As discussed above, any other protocols, including, for example, HTTP, MQTT, and CoAP, may be used to transfer the message containing the code execution request to the frontend 120. The frontend 120 may also receive the request to execute such user codes when an event is detected, such as an event that the user has registered to trigger automatic request generation. For example, the user may have registered the user code with an auxiliary service 106 and specified that whenever a particular event occurs (e.g., a new file is uploaded), the request to execute the user code is sent to the frontend 120. Alternatively, the user may have registered a timed job (e.g., execute the user code every 24 hours). In such an example, when the scheduled time arrives for the timed job, the request to execute the user code may be sent to the frontend 120. In yet another example, the frontend 120 may have a queue of incoming code execution requests, and when the user's batch job is removed from the virtual compute system's work queue, the frontend 120 may process the user request. In yet another example, the request may originate from another component within the virtual compute system 110 or other servers or services not illustrated in
A user request may specify one or more third-party libraries (including native libraries) to be used along with the user code. In one embodiment, the user request is a ZIP file containing the user code and any libraries (and/or identifications of storage locations thereof). In some embodiments, the user request includes metadata that indicates the program code to be executed, the language in which the program code is written, the user associated with the request, and/or the computing resources (e.g., memory, etc.) to be reserved for executing the program code. For example, the program code may be provided with the request, previously uploaded by the user, provided by the virtual compute system 110 (e.g., standard routines), and/or provided by third parties. In some embodiments, such resource-level constraints (e.g., how much memory is to be allocated for executing a particular user code) are specified for the particular user code, and may not vary over each execution of the user code. In such cases, the virtual compute system 110 may have access to such resource-level constraints before each individual request is received, and the individual requests may not specify such resource-level constraints. In some embodiments, the user request may specify other constraints such as permission data that indicates what kind of permissions that the request has to execute the user code. Such permission data may be used by the virtual compute system 110 to access private resources (e.g., on a private network).
In some embodiments, the user request may specify the behavior that should be adopted for handling the user request. In such embodiments, the user request may include an indicator for enabling one or more execution modes in which the user code associated with the user request is to be executed. For example, the request may include a flag or a header for indicating whether the user code should be executed in a debug mode in which the debugging and/or logging output that may be generated in connection with the execution of the user code is provided back to the user (e.g., via a console user interface). In such an example, the virtual compute system 110 may inspect the request and look for the flag or the header, and if it is present, the virtual compute system 110 may modify the behavior (e.g., logging facilities) of the container in which the user code is executed, and cause the output data to be provided back to the user. In some embodiments, the behavior/mode indicators are added to the request by the user interface provided to the user by the virtual compute system 110. Other features such as source code profiling, remote debugging, etc. may also be enabled or disabled based on the indication provided in the request.
In some embodiments, the virtual compute system 110 may include multiple frontends 120. In such embodiments, a load balancer may be provided to distribute the incoming requests to the multiple frontends 120, for example, in a round-robin fashion. In some embodiments, the manner in which the load balancer distributes incoming requests to the multiple frontends 120 may be based on the state of the warming pool 130A and/or the active pool 140A. For example, if the capacity in the warming pool 130A is deemed to be sufficient, the requests may be distributed to the multiple frontends 120 based on the individual capacities of the frontends 120 (e.g., based on one or more load balancing restrictions). On the other hand, if the capacity in the warming pool 130A is less than a threshold amount, one or more of such load balancing restrictions may be removed such that the requests may be distributed to the multiple frontends 120 in a manner that reduces or minimizes the number of virtual machine instances taken from the warming pool 130A. For example, even if, according to a load balancing restriction, a request is to be routed to Frontend A, if Frontend A needs to take an instance out of the warming pool 130A to service the request but Frontend B can use one of the instances in its active pool to service the same request, the request may be routed to Frontend B.
Warming Pool Manager
The warming pool manager 130 ensures that virtual machine instances are ready to be used by the worker manager 140 when the virtual compute system 110 receives a request to execute user code on the virtual compute system 110. In the example illustrated in
As shown in
In some embodiments, the virtual machine instances in the warming pool 130A may be used to serve any user's request. In one embodiment, all the virtual machine instances in the warming pool 130A are configured in the same or substantially similar manner. In another embodiment, the virtual machine instances in the warming pool 130A may be configured differently to suit the needs of different users. For example, the virtual machine instances may have different operating systems, different language runtimes, and/or different libraries loaded thereon. In yet another embodiment, the virtual machine instances in the warming pool 130A may be configured in the same or substantially similar manner (e.g., with the same OS, language runtimes, and/or libraries), but some of those instances may have different container configurations. For example, two instances may have runtimes for both Python and Ruby, but one instance may have a container configured to run Python code, and the other instance may have a container configured to run Ruby code. In some embodiments, multiple warming pools 130A, each having identically-configured virtual machine instances, are provided.
The warming pool manager 130 may pre-configure the virtual machine instances in the warming pool 130A, such that each virtual machine instance is configured to satisfy at least one of the operating conditions that may be requested or specified by the user request to execute program code on the virtual compute system 110. In one embodiment, the operating conditions may include program languages in which the potential user codes may be written. For example, such languages may include Java, JavaScript, Python, Ruby, and the like. In some embodiments, the set of languages that the user codes may be written in may be limited to a predetermined set (e.g., set of 4 languages, although in some embodiments sets of more or less than four languages are provided) in order to facilitate pre-initialization of the virtual machine instances that can satisfy requests to execute user codes. For example, when the user is configuring a request via a user interface provided by the virtual compute system 110, the user interface may prompt the user to specify one of the predetermined operating conditions for executing the user code. In another example, the service-level agreement (SLA) for utilizing the services provided by the virtual compute system 110 may specify a set of conditions (e.g., programming languages, computing resources, etc.) that user requests should satisfy, and the virtual compute system 110 may assume that the requests satisfy the set of conditions in handling the requests. In another example, operating conditions specified in the request may include: the amount of compute power to be used for processing the request; the type of the request (e.g., HTTP vs. a triggered event); the timeout for the request (e.g., threshold time after which the request may be terminated); security policies (e.g., may control which instances in the warming pool 130A are usable by which user); scheduling information (e.g., the time by which the virtual compute system is requested to execute the program code, the time after which the virtual compute system is requested to execute the program code, the temporal window within which the virtual compute system is requested to execute the program code, etc.), etc.
Worker Manager
The worker manager 140 manages the instances used for servicing incoming code execution requests. In the example illustrated in
In the example illustrated in
As shown in
In the example of
Although the components inside the containers 156B, 157A, 157B, 157C, 158A, 158B, 159A are not illustrated in the example of
After a request has been successfully processed by the frontend 120, the worker manager 140 finds capacity to service the request to execute user code on the virtual compute system 110. For example, if there exists a particular virtual machine instance in the active pool 140A that has a container with the same user code loaded therein (e.g., code 156A-3 shown in the container 156A), the worker manager 140 may assign the container to the request and cause the user code to be executed in the container. Alternatively, if the user code is available in the local cache of one of the virtual machine instances (e.g., stored on the instance 158 but does not belong to any individual containers), the worker manager 140 may create a new container on such an instance, assign the container to the request, and cause the user code to be loaded and executed in the container.
If the worker manager 140 determines that the user code associated with the request is not found on any of the instances (e.g., either in a container or the local cache of an instance) in the active pool 140A, the worker manager 140 may determine whether any of the instances in the active pool 140A is currently assigned to the user associated with the request and has compute capacity to handle the current request. If there is such an instance, the worker manager 140 may create a new container on the instance and assign the container to the request. Alternatively, the worker manager 140 may further configure an existing container on the instance assigned to the user, and assign the container to the request. For example, the worker manager 140 may determine that the existing container may be used to execute the user code if a particular library demanded by the current user request is loaded thereon. In such a case, the worker manager 140 may load the particular library and the user code onto the container and use the container to execute the user code.
If the active pool 140A does not contain any instances currently assigned to the user, the worker manager 140 pulls a new virtual machine instance from the warming pool 130A, assigns the instance to the user associated with the request, creates a new container on the instance, assigns the container to the request, and causes the user code to be downloaded and executed on the container.
In some embodiments, the virtual compute system 110 is adapted to begin execution of the user code shortly after it is received (e.g., by the frontend 120). A time period can be determined as the difference in time between initiating execution of the user code (e.g., in a container on a virtual machine instance associated with the user) and receiving a request to execute the user code (e.g., received by a frontend). The virtual compute system 110 is adapted to begin execution of the user code within a time period that is less than a predetermined duration. In one embodiment, the predetermined duration is 500 ms. In another embodiment, the predetermined duration is 300 ms. In another embodiment, the predetermined duration is 100 ms. In another embodiment, the predetermined duration is 50 ms. In another embodiment, the predetermined duration is 10 ms. In another embodiment, the predetermined duration may be any value chosen from the range of 10 ms to 500 ms. In some embodiments, the virtual compute system 110 is adapted to begin execution of the user code within a time period that is less than a predetermined duration if one or more conditions are satisfied. For example, the one or more conditions may include any one of: (1) the user code is loaded on a container in the active pool 140A at the time the request is received; (2) the user code is stored in the code cache of an instance in the active pool 140A at the time the request is received; (3) the active pool 140A contains an instance assigned to the user associated with the request at the time the request is received; or (4) the warming pool 130A has capacity to handle the request at the time the request is received. In some embodiments, instead of initiating the requested code execution as soon as the code execution request is received, the virtual compute system 110 may schedule the code execution according to the scheduling information provided by the request. For example, the request may specify a temporal window (e.g., between 3:00 AM to 4:00 AM next Monday) within which the virtual compute system 110 is requested to perform the code execution, and the virtual compute system 110 may schedule the code execution based on certain performance considerations (e.g., workload, latency, etc.). The scheduling process is described in greater detail below with respect to
The user code may be downloaded from an auxiliary service 106 such as the storage service 108 of
Once the worker manager 140 locates one of the virtual machine instances in the warming pool 130A that can be used to serve the user code execution request, the warming pool manager 130 or the worker manager 140 takes the instance out of the warming pool 130A and assigns it to the user associated with the request. The assigned virtual machine instance is taken out of the warming pool 130A and placed in the active pool 140A. In some embodiments, once the virtual machine instance has been assigned to a particular user, the same virtual machine instance cannot be used to service requests of any other user. This provides security benefits to users by preventing possible co-mingling of user resources. Alternatively, in some embodiments, multiple containers belonging to different users (or assigned to requests associated with different users) may co-exist on a single virtual machine instance. Such an approach may improve utilization of the available compute capacity. In some embodiments, the virtual compute system 110 may maintain a separate cache in which user codes are stored to serve as an intermediate level of caching system between the local cache of the virtual machine instances and a web-based network storage (e.g., accessible via the network 104).
After the user code has been executed, the worker manager 140 may tear down the container used to execute the user code to free up the resources it occupied to be used for other containers in the instance. Alternatively, the worker manager 140 may keep the container running to use it to service additional requests from the same user. For example, if another request associated with the same user code that has already been loaded in the container is received, the request can be assigned to the same container, thereby eliminating the delay associated with creating a new container and loading the user code in the container. In some embodiments, the worker manager 140 may tear down the instance in which the container used to execute the user code was created. Alternatively, the worker manager 140 may keep the instance running to use it to service additional requests from the same user. The determination of whether to keep the container and/or the instance running after the user code is done executing may be based on a threshold time, the type of the user, average request volume of the user, periodicity information (e.g., containers/instances in the active pool 140A not currently executing user code thereon can be (i) kept alive if the periodicity information indicates that additional requests are expected to arrive soon or (ii) terminated if the periodicity information indicates that additional requests are not likely to arrive soon enough to justify keeping the containers/instances alive), and/or other operating conditions. For example, after a threshold time has passed (e.g., 5 minutes, 30 minutes, 1 hour, 24 hours, 30 days, etc.) without any activity (e.g., running of the code), the container and/or the virtual machine instance is shutdown (e.g., deleted, terminated, etc.), and resources allocated thereto are released. In some embodiments, the threshold time passed before a container is torn down is shorter than the threshold time passed before an instance is torn down.
In some embodiments, the virtual compute system 110 may provide data to one or more of the auxiliary services 106 as it services incoming code execution requests. For example, the virtual compute system 110 may communicate with the monitoring/logging/billing services 107. The monitoring/logging/billing services 107 may include: a monitoring service for managing monitoring information received from the virtual compute system 110, such as statuses of containers and instances on the virtual compute system 110; a logging service for managing logging information received from the virtual compute system 110, such as activities performed by containers and instances on the virtual compute system 110; and a billing service for generating billing information associated with executing user code on the virtual compute system 110 (e.g., based on the monitoring information and/or the logging information managed by the monitoring service and the logging service). In addition to the system-level activities that may be performed by the monitoring/logging/billing services 107 (e.g., on behalf of the virtual compute system 110) as described above, the monitoring/logging/billing services 107 may provide application-level services on behalf of the user code executed on the virtual compute system 110. For example, the monitoring/logging/billing services 107 may monitor and/or log various inputs, outputs, or other data and parameters on behalf of the user code being executed on the virtual compute system 110. Although shown as a single block, the monitoring, logging, and billing services 107 may be provided as separate services.
In some embodiments, the worker manager 140 may perform health checks on the instances and containers managed by the worker manager 140 (e.g., those in the active pool 140A). For example, the health checks performed by the worker manager 140 may include determining whether the instances and the containers managed by the worker manager 140 have any issues of (1) misconfigured networking and/or startup configuration, (2) exhausted memory, (3) corrupted file system, (4) incompatible kernel, and/or any other problems that may impair the performance of the instances and the containers. In one embodiment, the worker manager 140 performs the health checks periodically (e.g., every 5 minutes, every 30 minutes, every hour, every 24 hours, etc.). In some embodiments, the frequency of the health checks may be adjusted automatically based on the result of the health checks. In other embodiments, the frequency of the health checks may be adjusted based on user requests. In some embodiments, the worker manager 140 may perform similar health checks on the instances and/or containers in the warming pool 130A. The instances and/or the containers in the warming pool 130A may be managed either together with those instances and containers in the active pool 140A or separately. In some embodiments, in the case where the health of the instances and/or the containers in the warming pool 130A is managed separately from the active pool 140A, the warming pool manager 130, instead of the worker manager 140, may perform the health checks described above on the instances and/or the containers in the warming pool 130A.
Scheduling Manager
The scheduling manager 150 monitors code execution requests received by the virtual compute system 110 (e.g., via the frontend 120) and schedules corresponding code executions. For example, the scheduling manager 150 may communicate with the frontend 120, the warming pool manager 130, and/or the worker manager 140 to schedule jobs (e.g., execution of user code on the virtual compute system 110) and/or manage the compute capacity in the warming pool 130A and/or the active pool 140A. Although the scheduling manager 150 is illustrated as a distinct component within the virtual compute system 110, part or all of the functionalities of the scheduling manager 150 may be performed by the frontend 120, the warming pool manager 130, and/or the worker manager 140. For example, the scheduling manager 150 may be implemented entirely within one of the other components of the virtual compute system 110 or in a distributed manner across the other components of the virtual compute system 110. In the example of
The scheduling manager 150 monitors code execution requests received by the virtual compute system 110 and identifies any periodicity exhibited by the incoming code execution requests. For example, the scheduling manager 150 may look for a pattern in the specific times at which code execution requests associated with the particular user account or user function are received. For example, the scheduling manager 150 may determine that the requests associated with a particular user account are received only between 3:00 AM and 3:15 AM (e.g., such requests may comprise daily maintenance operations). In another example, the scheduling manager 150 may determine that the requests associated with a particular program code are received only on Sundays (e.g., such requests may comprise weekly backup operations). In another example, the scheduling manager 150 may determine that the system-wide traffic is generally highest from 7:00 PM to 9:00 PM. In some cases, incoming code execution requests associated with certain user accounts or user functions may be received throughout the day or without exhibiting any identifiable periodicity.
In some embodiments, the scheduling manager 150 detects the periodicity using regression models of the incoming traffic patterns. In other embodiments, the scheduling manager 150 may reverse engineer the periodicity from the log data (e.g., scheduling management data 150A) generated by the scheduling manager 150 based on the parameters associated with the incoming code execution requests (e.g., time of receipt, associated user account, associated user function, maximum duration, amount of resources to be allocated, etc.). For example, the scheduling manager 150 may periodically analyze the scheduling management data 150A (e.g., daily, weekly, monthly, yearly, etc.) to identify the periodicity exhibited by the incoming code execution requests. In some embodiments, a human operator may notice the periodicity in incoming code execution requests and input certain periodicity parameters into the virtual compute system 110 (e.g., expected time of receipt, associated user account, associated user function, etc.). Based on the identified periodicity, the scheduling manager 150 may adjust the capacity maintained on the virtual compute system 110. The process of identifying the periodicity and adjusting capacity maintained on the virtual compute system 110 is described in greater detail below with reference to
The scheduling manager 150 may also schedule and manage code execution on the virtual compute system 110. If a batch of code executions are requested to be performed at the same time or within a short span of time, the scheduling manager 150 may reschedule some of the code executions depending on the degree of flexibility provided by the specified timeframe for executing the user code. One way of obtaining the flexibility in the timing of execution is to build a range into the request such that any request to schedule a cloud function to be executed at a specified time actually means that the cloud function will be executed within a time period before and after the specified time. For example, if a program code is requested to be executed at 3:00 PM, the virtual compute system 110 may, by default, have the flexibility to execute the code any time between 2:50 PM and 3:10 PM. The users of the virtual compute system 110 may be notified of this range. The range may vary depending on the implementation.
In some embodiments, the cost associated with executing user functions on the virtual compute system 110 may vary depending on the degree of temporal flexibility specified by the request. For example, if the user requested that a program code be run between 11:00 PM and 1:00 AM, the cost might be 0.01 cents per execution. If the user requested that the program code be run between 11:55 PM and 1:05 AM, the cost might be 0.02 cents per execution. If the user requested that the program code be run exactly at 12:00 AM, the cost might be 0.05 cents per execution. Another example that provides the virtual compute system 110 a lot of flexibility is to allow the users to specify that the user functions can be run whenever the traffic is low, as determined by the request arrival rates, the number of concurrent jobs being processed, or other mechanisms (which may be less expensive than specifying a window).
The compute system 110 may present to the user (e.g., via a graphical user interface that allows the user the schedule code executions) the costs associated with the various ranges that can be specified for the code execution requests. The flexibility in the start times provides the virtual compute system 110 the ability to schedule the code executions when the incoming traffic is low, thereby reducing the amount of burst capacity that the virtual compute system 110 needs to provide.
In some embodiments, rather than using a range to obtain flexibility, the user may specify a point in time before or after which the virtual compute system 110 is requested to run the program. For example, the request may specify that the virtual compute system 110 should run a program code sometime after October 10th (e.g., on the specified date or later). In another example, the request may specify that the virtual compute system 110 should finish running a program code sometime before October 8th (e.g., finish executing the program code on or before October 8th). In such an example, the virtual compute system 110 may ensure that the code execution is initiated at least an amount of time equal to the maximum duration before the specified deadline. In yet another example, the request may specify that the virtual compute system 110 should start running a program code sometime before October 8th (e.g., initiate execution of the program code on or before October 8th, but need not finish on or before October 8th). In some embodiments, each code execution request specifies a maximum duration after which the execution of the program code should be considered to have timed out. In such embodiments, the virtual compute system 110 may utilize the specified maximum duration to spread out the workload so that the virtual compute system 110 is not overloaded at any given point in time. The process of scheduling code executions in a flexible manner is described in greater detail below with reference to
The scheduling manager 150 may include a request and capacity monitoring unit for monitoring the requests received by the virtual compute system 110, and a schedule and capacity adjustment unit for scheduling and managing code execution and capacity on the virtual compute system 110. An example configuration of the scheduling manager 150 is described in greater detail below with reference to
Illustrative Example of Processing Periodic Jobs
With reference to
The example on the left side of
The example on the right side of
Illustrative Example of Scheduling Jobs
With reference to
The example on the left side of
The example on the right side of
General Architecture of Scheduling Manager
The memory 180 may contain computer program instructions (grouped as modules in some embodiments) that the processing unit 190 executes in order to implement one or more aspects of the present disclosure. The memory 180 generally includes RAM, ROM and/or other persistent, auxiliary or non-transitory computer-readable media. The memory 180 may store an operating system 184 that provides computer program instructions for use by the processing unit 190 in the general administration and operation of the scheduling manager 150. The memory 180 may further include computer program instructions and other information for implementing aspects of the present disclosure. For example, in one embodiment, the memory 180 includes a user interface unit 182 that generates user interfaces (and/or instructions therefor) for display upon a computing device, e.g., via a navigation and/or browsing interface such as a browser or application installed on the computing device. In addition, the memory 180 may include and/or communicate with one or more data repositories (not shown), for example, to access user program codes and/or libraries.
In addition to and/or in combination with the user interface unit 182, the memory 180 may include a request and capacity monitoring unit 186 and a schedule and capacity adjustment unit 188 that may be executed by the processing unit 190. In one embodiment, the user interface unit 182, request and capacity monitoring unit 186, and schedule and capacity adjustment unit 188 individually or collectively implement various aspects of the present disclosure, e.g., monitoring incoming code execution requests, determining whether the incoming code execution requests exhibit any periodicity, causing a reduced amount of idle capacity to be maintained in the warming pool 130A, acquiring compute capacity for handling incoming code execution requests just before such incoming code execution requests are received (e.g., based on their periodicity), scheduling multiple jobs such that they do not overlap with each other, etc. as described further below.
The request and capacity monitoring unit 186 monitors incoming code execution requests. For example, the request and capacity monitoring unit 186 monitors incoming code execution requests and identifies any periodicity exhibited by some or all of the incoming code execution requests that may be used to better manage the capacity on the virtual compute system 110 (e.g., reduce the number of capacity maintained in the warming pool 130A). The request and capacity monitoring unit 186 may keep track of the time at which each of the incoming code execution requests are received and the user accounts and/or the user functions associated with such requests along with requested and actual duration or other resource consumption, such as memory.
The schedule and capacity adjustment unit 188 schedules jobs and adjusts capacity in the warming pool 130A and/or the active pool 140A. for example, based on the periodicity identified by the request and capacity monitoring unit 186, the schedule and capacity adjustment unit 188 may cause the amount of capacity maintained in the warming pool 130A to be reduced. Further, the scheduling capacity adjustment unit 188 may cause additional capacity to be added to the active pool 140A shortly before the time at which the code execution requests identified as being periodic are expected to be received by the virtual compute system 110 or cause capacity in the active pool 140A to be retained longer than usual in order to service an anticipated future request based on periodicity analysis/predictions.
While the request and capacity monitoring unit 186 and the schedule and capacity adjustment unit 188 are shown in
Example Routine for Managing Schedule Code Execution Requests
Turning now to
At block 502 of the illustrative routine 500, the scheduling manager 150 monitors incoming code execution requests that are received by the virtual compute system 110, for example, to identify any periodicity exhibited by the incoming requests (e.g., any indication that at least some of the incoming requests are periodic in nature). The scheduling manager 150 may record the time at which each request is received by the virtual compute system 110 in a database (e.g., scheduling management data 150A) along with the identity of the program code associated with the request, the user account associated with the request, the maximum duration associated with the request, and/or any other parameters associated with the request, along with actual resource consumption, including running tie (duration), memory usage, throttles applied, security tests passed or failed, etc.
Next, at block 504, the scheduling manager 150 determines whether any periodicity is exhibited by at least some of the incoming code execution requests received by the virtual compute system 110. For example, the scheduling manager 150 may determine that the requests associated with a particular user account are received only between 3:00 AM and 3:15 AM (e.g., such requests may comprise daily maintenance operations). In another example, the scheduling manager 150 may determine that the requests associated with a particular program code are received only on Sundays (e.g., such requests may comprise weekly backup operations). In another example, the scheduling manager 150 may determine that the system-wide traffic is generally highest from 7:00 PM to 9:00 PM. In some cases, incoming code execution requests associated with certain user accounts or user functions may be received throughout the day or without exhibiting any identifiable periodicity. Even in such cases, by identifying at least some code execution requests that exhibit identifiable periodicity, the virtual compute system 110 may be able to treat such code execution requests as scheduled requests. Such periodic or scheduled requests result in cost savings for the virtual compute system 110 because if the virtual compute system 110 when the requests will be received, the virtual compute system 110 need not maintain idle compute capacity (which may be costly) just to be able to handle unpredictable burst traffic; it can simply acquire compute capacity when (or just before) the requests arrive at the virtual compute system 110. In some embodiments, the scheduling manager 150 may process the logs and/or metrics generated by the virtual compute system 110 based on the incoming code execution requests to determine whether any periodicity is exhibited by any of such code execution requests.
If the scheduling manager 150 determines that at least some of the code execution requests received by the virtual compute system 110 exhibit a degree of periodicity, the routine 500 proceeds to block 506, where the scheduling manager 150 causes a reduced amount of idle compute capacity (or unallocated compute capacity that is not assigned to a particular user account or is between jobs) to be maintained (e.g., in the warming pool 130A). For example, the reduced amount may be proportional to the number of code execution requests identified as being periodic. If none of the code execution requests is identified as being periodic, the idle compute capacity maintained in the warming pool 130A may not be reduced at all. On the other hand, if all of the code execution requests are identified as being periodic, all the idle compute capacity maintained in the warming pool 130A may be removed. Similarly, if half of the code execution requests are identified as being periodic, the amount of idle compute capacity maintained in the warming pool 130A may be reduced to half of the amount normally maintained in the warming pool 130A. If the scheduling manager 150 determines that none of the code execution requests exhibits any periodicity, the routine 500 proceeds to block 502, and the scheduling manager 150 continues to monitor incoming code execution requests. In some embodiments, the scheduling manager 150 (or other components of the virtual compute system 110 such as the warming pool manager 130) causes a reduced amount of idle compute capacity to be maintained by refraining from adding additional virtual machine instances to the warming pool 130A until the number of virtual machine instances in the warming pool 130A reaches a number corresponding to the reduced amount. For example, if the scheduling manager 150 determines that the idle capacity maintained in the warming pool 130A should be reduced by half based on the periodicity exhibited by the incoming code execution requests, the scheduling manager 150 may refrain from adding additional capacity to the warming pool 130A until the amount of capacity in the warming pool 130A becomes half the amount that was previously being maintained in the warming pool 130A. In some cases, the scheduling manager 150 may actively shut down some of the virtual machine instances in the warming pool 130A to reach a reduced number. In other cases, the scheduling manager 150 may cause instances to be moved more freely (or aggressively) from the warming pool 130A to the active pool 140A. In some embodiments, the reduction in the amount of idle compute capacity may result from the active pool 140A. For example, virtual machine instances placed in the active pool 140A but not currently executing user code thereon that would otherwise be kept alive (e.g., without the periodicity information) in an idle state in the active pool 140A may be spun down, based on the periodicity detected at block 504 (e.g., a determination that no request that would use the currently idle instance in the active pool 140A is expected to arrive anytime soon).
At block 508, the scheduling manager 150 causes additional compute capacity to be acquired for handling the incoming code execution requests (or the next request that exhibits the same periodicity as the incoming code execution requests determined to exhibit some degree of periodicity), which are identified as being periodic, at the anticipated time of receipt. For example, if, based on the identified periodicity, the virtual compute system 110 is expected to receive a batch of code execution requests at 3:00 PM, the scheduling manager 150 may cause additional compute capacity (e.g., one or more virtual machine instances) sufficient to handle the batch of code execution requests to be acquired (e.g., by sending a request to the instance provisioning service 109 or by instructing another component of the virtual compute system 110 to do so) sometime before the time the batch of requests are expected to arrive (e.g., 2:59 PM, or at a time that would allow the virtual compute system 110 to configure the compute capacity to handle the batch of requests by 3:00 PM). For example, the threshold amount of time before which the additional compute capacity is acquired and pre-initialized may vary based on the program code, the user account, or the request. In some cases, the acquired compute capacity may be added directly to the active pool 140A. For example, if the batch of code execution requests are associated with a user whose execution settings are known, the acquired compute capacity may be pre-initialized and placed in the active pool 140 so that the compute capacity can be used as soon as the requests arrive. In some embodiments, additional compute capacity may be added by keeping alive one or more virtual machine instances placed in the active pool 140A but not currently executing user code thereon that would otherwise be terminated (e.g., without the periodicity information) in an idle state in the active pool 140A in anticipation of the code execution requests identified as being periodic. In other cases, the acquired compute capacity may be added to the warming pool 130A. For example, if the scheduling manager 150 determines that a system-wide increase in incoming code execution requests is expected in 10 minutes, the scheduling manager 150 may acquire additional capacity and add such capacity to the warming pool 130A so the added capacity may be used to handle a more diverse group of requests. In some embodiments, the scheduling manager 150 (or other components of the virtual compute system 110 such as the worker manager 140) may create one or more containers on the virtual machine instance(s) acquired for executing user functions associated with the batch of requests, and load the user functions onto the container(s) before the batch of requests are received by the virtual compute system 110. By doing so, the scheduling manager 150 allows the user functions to be executed as soon as the batch of requests are received, without having to first acquire virtual machine instances, create one or more containers thereon, and load one or more user functions onto the containers, thereby reducing the delay associated with executing the user functions on the virtual compute system 110.
While the routine 500 of
Example Routine for Scheduling Code Execution Requests Based on Temporal Criteria
Turning now to
At block 602 of the illustrative routine 600, the scheduling manager 150 receives a first job request having a first time frame for executing a first program code. For example, the first job request may request that a backup routine be executed at 3:00 AM tomorrow. In some embodiments, the time frame specified by the request may be one of (i) a time by which the virtual compute system is requested to execute the first program code (e.g., “execute the backup routine by 3:00 AM but you can get started any time before that”), (ii) a time after which the virtual compute system is requested to execute the first program code (e.g., “execute the backup routine after 3:00 AM but you can take however much time before you initiate the backup routine”), or (iii) a temporal window within which the virtual compute system is requested to execute the first program code (e.g., “execute the backup routine between 2:30 AM and 3:30 AM” or “execute the backup routine at 3:00 AM plus or minus 30 minutes”). In some embodiments, the time frame may be provided in the request itself. In other embodiments, the scheduling manager 150 may determine the time frame associated with a request by looking up the time frame using the user account associated with the request or the program code associated with the request, or by using system-wide settings or published system-wide, per-account, or per-function SLAs. In some embodiments, the scheduling manager 150 is configured to provide, via a user interface, an option of selecting among various degrees of temporal flexibility (e.g., options (i)-(iii) listed above). In some embodiments, the varying degrees of temporal flexibility may be associated with varying amounts of cost associated with executing user functions on the virtual compute system 110. For example, it may cost the user 0.01 cents per execution if the user specifies a 2-hour range within which a requested user function is to be executed, but cause the user 0.1 cents per execution if the user specifies an exact point in time at which the requested user function is to be executed.
At block 604, the scheduling manager 150 receives a second job request having a second time frame for executing a second program code. For example the second job request may request that a file compression routine be executed at 3:00 AM tomorrow. As discussed above, the time frame specified by the request may be one of (i) a time by which the virtual compute system is requested to execute the second program code (e.g., “execute the file compression routine by 3:00 AM but you can get started any time before that”), (ii) a time after which the virtual compute system is requested to execute the second program code (e.g., “execute the file compression routine after 3:00 AM but you can take however much time before you initiate the file compression”), or (iii) a temporal window within which the virtual compute system is requested to execute the second program code (e.g., “execute the file compression routine between 2:30 AM and 3:30 AM” or “execute the file compression routine at 3:00 AM plus or minus 30 minutes”). Although the backup routine and the file compression routine are used herein as examples, any other program code, user function, etc. may be used. In some embodiments, the requests also specify a maximum duration after which the corresponding code execution should be considered to have timed out. For example, such a maximum duration may provide the scheduling manager 150 the assurance that a user function will not still be running after a period of time equal to the maximum duration has passed since the time at which the execution of the user function was initiated.
At block 606, the scheduling manager 150 schedules the first and second jobs such that the first and second jobs do not overlap with each other. In the example above, even though the specified time frame for each of the first and second job requests may refer to 3:00 AM, there may be some flexibility in scheduling the jobs. If both of the job requests specify that the corresponding routines should be executed at 3:00 AM or sometime after that, the scheduling manager 150 may schedule the backup routine to be executed at 3:00 AM and the file compression routine to be executed at 3:10 AM. If both of the job requests specify that the corresponding routines should finish executing by 3:00 AM or sometime before that, the scheduling manager 150 may schedule the backup routine to be executed at 2:40 AM and the file compression routine to be executed at 2:50 AM. If both of the job requests specify that the corresponding routines should be executed between 2:30 AM and 3:30 AM, the scheduling manager 150 may schedule the backup routine to be executed at 2:50 AM and the file compression routine to be executed at 3:00 AM. In some embodiments, if both of the job requests specify that the corresponding routines must finish executing before 3:00 AM, neither job can be scheduled after (3:00 AM-(max duration of the respective job)).
While the routine 600 of
Example Routine for Scheduling Jobs Based on Execution Requirements
Turning now to
At block 702 of the illustrative routine 700, the scheduling manager 150 receives a request to execute a first job having a first set of execution requirements. For example, the first set of execution requirements may include the amount of computing resources (e.g., memory, CPU, network, etc.) used to execute the first job. In another example, the first set of execution requirements may include temporal or spatial resource such as how much time is needed to execute the first job, and how much compute capacity is needed to execute the first job, etc. For example, the first job may be a file compression routine that uses 128 MB of memory.
At block 704, the scheduling manager 150 the scheduling manager 150 receives a request to execute a second job having a second set of execution requirements. For example, the second set of execution requirements may include the amount of computing resources (e.g., memory, CPU, network, etc.) used to execute the second job. In another example, the second set of execution requirements may include temporal or spatial resource such as how much time is needed to execute the second job, and how much compute capacity is needed to execute the second job, etc. For example, the second job may be an image processing routine that uses 512 MB of memory.
At block 706, the scheduling manager 150 determines one or more scheduling criteria based on the first and second sets of execution requirements. For example, the scheduling manager 150, having determined that the first job uses 128 MB of memory and the second job uses 512 MB of memory, may further determine that for the first and second jobs to be executed simultaneously (or executed such that the jobs temporally overlap), at least 640 MB of memory is needed. In other words, the scheduling criteria may be that (i) the first job can be scheduled to be executed as long as the virtual compute system 110 has at least 128 MB of free memory, (ii) the second job can be scheduled to be executed as long as the virtual compute system 110 has at least 512 MB of free memory, and (iii) the first and second jobs can be scheduled to be executed in a temporally overlapping manner as long as the virtual compute system 110 has at least 640 MB of free memory.
At block 708, the scheduling manager 150 schedules the first and second jobs such that the scheduling criteria are satisfied. In the example discussed above, the scheduling manager 150 may schedule the first and second jobs to be executed simultaneously if the virtual compute system has 1 GB of memory at the time the first and second jobs are to be executed. If the virtual compute system 110 has only 600 MB of memory available, the scheduling manager 150 may schedule the first and second jobs such that the executions do not overlap. Although memory is used to illustrate the resource contention between the first and second jobs, the techniques can be extended to any other resources that may be utilized by both the first and second jobs.
While the routine 700 of
Other Considerations
It will be appreciated by those skilled in the art and others that all of the functions described in this disclosure may be embodied in software executed by one or more physical processors of the disclosed components and mobile communication devices. The software may be persistently stored in any type of non-volatile storage.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. It will further be appreciated that the data and/or components described above may be stored on a computer-readable medium and loaded into memory of the computing device using a drive mechanism associated with a computer readable storage medium storing the computer executable components such as a CD-ROM, DVD-ROM, or network interface. Further, the component and/or data can be included in a single device or distributed in any manner. Accordingly, general purpose computing devices may be configured to implement the processes, algorithms, and methodology of the present disclosure with the processing and/or execution of the various data and/or components described above.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4949254 | Shorter | Aug 1990 | A |
5283888 | Dao et al. | Feb 1994 | A |
5970488 | Crowe et al. | Oct 1999 | A |
6708276 | Yarsa et al. | Mar 2004 | B1 |
7036121 | Casabona et al. | Apr 2006 | B1 |
7665090 | Tormasov et al. | Feb 2010 | B1 |
7707579 | Rodriguez | Apr 2010 | B2 |
7730464 | Trowbridge | Jun 2010 | B2 |
7774191 | Berkowitz et al. | Aug 2010 | B2 |
7823186 | Pouliot | Oct 2010 | B2 |
7886021 | Scheifler et al. | Feb 2011 | B2 |
8010990 | Ferguson et al. | Aug 2011 | B2 |
8024564 | Bassani et al. | Sep 2011 | B2 |
8046765 | Cherkasova et al. | Oct 2011 | B2 |
8051180 | Mazzaferri et al. | Nov 2011 | B2 |
8051266 | DeVal | Nov 2011 | B2 |
8065676 | Sahai et al. | Nov 2011 | B1 |
8095931 | Chen et al. | Jan 2012 | B1 |
8127284 | Meijer et al. | Feb 2012 | B2 |
8146073 | Sinha | Mar 2012 | B2 |
8166304 | Murase et al. | Apr 2012 | B2 |
8171473 | Lavin | May 2012 | B2 |
8209695 | Pruyne et al. | Jun 2012 | B1 |
8336079 | Budko et al. | Dec 2012 | B2 |
8429282 | Ahuja | Apr 2013 | B1 |
8448165 | Conover | May 2013 | B1 |
8613070 | Borzycki et al. | Dec 2013 | B1 |
8631130 | Jackson | Jan 2014 | B2 |
8677359 | Cavage et al. | Mar 2014 | B1 |
8694996 | Cawlfield et al. | Apr 2014 | B2 |
8719415 | Sirota et al. | May 2014 | B1 |
8725702 | Raman et al. | May 2014 | B1 |
8756696 | Miller | Jun 2014 | B1 |
8769519 | Leitman et al. | Jul 2014 | B2 |
8806468 | Meijer et al. | Aug 2014 | B2 |
8819679 | Agarwal et al. | Aug 2014 | B2 |
8825964 | Sopka et al. | Sep 2014 | B1 |
8904008 | Calder et al. | Dec 2014 | B2 |
8997093 | Dimitrov | Mar 2015 | B2 |
9027087 | Ishaya et al. | May 2015 | B2 |
9038068 | Engle et al. | May 2015 | B2 |
9086897 | Oh et al. | Jun 2015 | B2 |
9092837 | Bala et al. | Jul 2015 | B2 |
9110732 | Forschmiedt et al. | Aug 2015 | B1 |
9112813 | Jackson | Aug 2015 | B2 |
9146764 | Wagner | Sep 2015 | B1 |
9183019 | Kruglick | Nov 2015 | B2 |
9208007 | Harper et al. | Dec 2015 | B2 |
9223561 | Orveillon et al. | Dec 2015 | B2 |
9223966 | Satish et al. | Dec 2015 | B1 |
9317689 | Aissi | Apr 2016 | B2 |
9323556 | Wagner | Apr 2016 | B2 |
9361145 | Wilson et al. | Jun 2016 | B1 |
9413626 | Reque et al. | Aug 2016 | B2 |
9436555 | Dornemann et al. | Sep 2016 | B2 |
9461996 | Hayton et al. | Oct 2016 | B2 |
9471775 | Wagner et al. | Oct 2016 | B1 |
9483335 | Wagner et al. | Nov 2016 | B1 |
9489227 | Oh et al. | Nov 2016 | B2 |
9537788 | Reque et al. | Jan 2017 | B2 |
9588790 | Wagner et al. | Mar 2017 | B1 |
9600312 | Wagner et al. | Mar 2017 | B2 |
9652306 | Wagner et al. | May 2017 | B1 |
9652617 | Evans et al. | May 2017 | B1 |
9661011 | Van Horenbeeck et al. | May 2017 | B1 |
9678773 | Wagner et al. | Jun 2017 | B1 |
9678778 | Youseff | Jun 2017 | B1 |
9715402 | Wagner et al. | Jul 2017 | B2 |
9727725 | Wagner et al. | Aug 2017 | B2 |
9733967 | Wagner et al. | Aug 2017 | B2 |
9760387 | Wagner et al. | Sep 2017 | B2 |
9785476 | Wagner et al. | Oct 2017 | B2 |
9811363 | Wagner | Nov 2017 | B1 |
9811434 | Wagner | Nov 2017 | B1 |
9830175 | Wagner | Nov 2017 | B1 |
9830193 | Wagner et al. | Nov 2017 | B1 |
9830449 | Wagner | Nov 2017 | B1 |
20020172273 | Baker | Nov 2002 | A1 |
20030071842 | King et al. | Apr 2003 | A1 |
20030084434 | Ren | May 2003 | A1 |
20040249947 | Novaes et al. | Dec 2004 | A1 |
20040268358 | Darling et al. | Dec 2004 | A1 |
20050044301 | Vasilevsky et al. | Feb 2005 | A1 |
20050132167 | Longobardi | Jun 2005 | A1 |
20050132368 | Sexton et al. | Jun 2005 | A1 |
20050193113 | Kokusho et al. | Sep 2005 | A1 |
20050193283 | Reinhardt et al. | Sep 2005 | A1 |
20050257051 | Richard | Nov 2005 | A1 |
20060123066 | Jacobs et al. | Jun 2006 | A1 |
20060129684 | Datta | Jun 2006 | A1 |
20060184669 | Vaidyanathan et al. | Aug 2006 | A1 |
20060200668 | Hybre et al. | Sep 2006 | A1 |
20060212332 | Jackson | Sep 2006 | A1 |
20060242647 | Kimbrel et al. | Oct 2006 | A1 |
20060248195 | Toumura et al. | Nov 2006 | A1 |
20070094396 | Takano et al. | Apr 2007 | A1 |
20070130341 | Ma | Jun 2007 | A1 |
20070255604 | Seelig | Nov 2007 | A1 |
20080028409 | Cherkasova et al. | Jan 2008 | A1 |
20080082977 | Araujo et al. | Apr 2008 | A1 |
20080104247 | Venkatakrishnan et al. | May 2008 | A1 |
20080104608 | Hyser | May 2008 | A1 |
20080126110 | Haeberle et al. | May 2008 | A1 |
20080126486 | Heist | May 2008 | A1 |
20080189468 | Schmidt et al. | Aug 2008 | A1 |
20080201711 | Amir Husain | Aug 2008 | A1 |
20090013153 | Hilton | Jan 2009 | A1 |
20090025009 | Brunswig et al. | Jan 2009 | A1 |
20090055810 | Kondur | Feb 2009 | A1 |
20090055829 | Gibson | Feb 2009 | A1 |
20090077569 | Appleton et al. | Mar 2009 | A1 |
20090125902 | Ghosh et al. | May 2009 | A1 |
20090158275 | Wang et al. | Jun 2009 | A1 |
20090193410 | Arthursson et al. | Jul 2009 | A1 |
20090198769 | Keller et al. | Aug 2009 | A1 |
20090204964 | Foley et al. | Aug 2009 | A1 |
20090288084 | Astete et al. | Nov 2009 | A1 |
20090300599 | Piotrowski | Dec 2009 | A1 |
20100023940 | Iwamatsu et al. | Jan 2010 | A1 |
20100031274 | Sim-Tang | Feb 2010 | A1 |
20100031325 | Maigne et al. | Feb 2010 | A1 |
20100036925 | Haffner | Feb 2010 | A1 |
20100064299 | Kacin et al. | Mar 2010 | A1 |
20100070678 | Zhang et al. | Mar 2010 | A1 |
20100070725 | Prahlad et al. | Mar 2010 | A1 |
20100114826 | Siddegowda | May 2010 | A1 |
20100115098 | De Baer et al. | May 2010 | A1 |
20100122343 | Ghosh | May 2010 | A1 |
20100131959 | Spiers et al. | May 2010 | A1 |
20100186011 | Magenheimer | Jul 2010 | A1 |
20100198972 | Umbehocker | Aug 2010 | A1 |
20100199285 | Medovich | Aug 2010 | A1 |
20100257116 | Mehta et al. | Oct 2010 | A1 |
20100269109 | Cartales | Oct 2010 | A1 |
20110010722 | Matsuyama | Jan 2011 | A1 |
20110029970 | Arasaratnam | Feb 2011 | A1 |
20110055378 | Ferris et al. | Mar 2011 | A1 |
20110055396 | DeHaan | Mar 2011 | A1 |
20110099551 | Fahrig et al. | Apr 2011 | A1 |
20110131572 | Elyashev et al. | Jun 2011 | A1 |
20110134761 | Smith | Jun 2011 | A1 |
20110141124 | Halls et al. | Jun 2011 | A1 |
20110153727 | Li | Jun 2011 | A1 |
20110153838 | Belkine et al. | Jun 2011 | A1 |
20110154353 | Theroux | Jun 2011 | A1 |
20110184993 | Chawla et al. | Jul 2011 | A1 |
20110265164 | Lucovsky | Oct 2011 | A1 |
20110314465 | Smith | Dec 2011 | A1 |
20110321033 | Kelkar et al. | Dec 2011 | A1 |
20120016721 | Weinman | Jan 2012 | A1 |
20120041970 | Ghosh et al. | Feb 2012 | A1 |
20120054744 | Singh et al. | Mar 2012 | A1 |
20120072914 | Ota | Mar 2012 | A1 |
20120096271 | Ramarathinam et al. | Apr 2012 | A1 |
20120096468 | Chakravorty et al. | Apr 2012 | A1 |
20120102307 | Wong | Apr 2012 | A1 |
20120102333 | Wong | Apr 2012 | A1 |
20120110155 | Adlung et al. | May 2012 | A1 |
20120110164 | Frey et al. | May 2012 | A1 |
20120110588 | Bieswanger et al. | May 2012 | A1 |
20120131379 | Tameshige et al. | May 2012 | A1 |
20120192184 | Burckart et al. | Jul 2012 | A1 |
20120197958 | Nightingale et al. | Aug 2012 | A1 |
20120233464 | Miller et al. | Sep 2012 | A1 |
20120331113 | Jain et al. | Dec 2012 | A1 |
20130014101 | Ballani et al. | Jan 2013 | A1 |
20130042234 | DeLuca et al. | Feb 2013 | A1 |
20130054804 | Jana | Feb 2013 | A1 |
20130054927 | Raj et al. | Feb 2013 | A1 |
20130055262 | Lubsey et al. | Feb 2013 | A1 |
20130061208 | Tsao et al. | Mar 2013 | A1 |
20130067494 | Srour et al. | Mar 2013 | A1 |
20130080641 | Lui et al. | Mar 2013 | A1 |
20130097601 | Podvratnik et al. | Apr 2013 | A1 |
20130111469 | B et al. | May 2013 | A1 |
20130132942 | Wang | May 2013 | A1 |
20130139152 | Chang et al. | May 2013 | A1 |
20130151648 | Luna | Jun 2013 | A1 |
20130179574 | Calder et al. | Jul 2013 | A1 |
20130179881 | Calder et al. | Jul 2013 | A1 |
20130179894 | Calder et al. | Jul 2013 | A1 |
20130185729 | Vasic et al. | Jul 2013 | A1 |
20130191924 | Tedesco | Jul 2013 | A1 |
20130198319 | Shen | Aug 2013 | A1 |
20130198743 | Kruglick | Aug 2013 | A1 |
20130205092 | Roy et al. | Aug 2013 | A1 |
20130219390 | Lee et al. | Aug 2013 | A1 |
20130227097 | Yasuda et al. | Aug 2013 | A1 |
20130227563 | Mcgrath | Aug 2013 | A1 |
20130227641 | White et al. | Aug 2013 | A1 |
20130232480 | Winterfeldt et al. | Sep 2013 | A1 |
20130239125 | Iorio | Sep 2013 | A1 |
20130263117 | Konik et al. | Oct 2013 | A1 |
20130275975 | Masuda et al. | Oct 2013 | A1 |
20130297964 | Hegdal et al. | Nov 2013 | A1 |
20130339950 | Ramarathinam et al. | Dec 2013 | A1 |
20130346946 | Pinnix | Dec 2013 | A1 |
20130346964 | Nobuoka et al. | Dec 2013 | A1 |
20130346987 | Raney et al. | Dec 2013 | A1 |
20130346994 | Chen et al. | Dec 2013 | A1 |
20130347095 | Barjatiya et al. | Dec 2013 | A1 |
20140007097 | Chin et al. | Jan 2014 | A1 |
20140019965 | Neuse et al. | Jan 2014 | A1 |
20140019966 | Neuse et al. | Jan 2014 | A1 |
20140040343 | Nickolov et al. | Feb 2014 | A1 |
20140040857 | Trinchini et al. | Feb 2014 | A1 |
20140040880 | Brownlow et al. | Feb 2014 | A1 |
20140059226 | Messerli et al. | Feb 2014 | A1 |
20140068611 | McGrath et al. | Mar 2014 | A1 |
20140082165 | Marr et al. | Mar 2014 | A1 |
20140101649 | Kamble et al. | Apr 2014 | A1 |
20140109087 | Jujare et al. | Apr 2014 | A1 |
20140109088 | Dournov et al. | Apr 2014 | A1 |
20140129667 | Ozawa | May 2014 | A1 |
20140130040 | Lemanski | May 2014 | A1 |
20140173614 | Konik et al. | Jun 2014 | A1 |
20140173616 | Bird et al. | Jun 2014 | A1 |
20140180862 | Certain et al. | Jun 2014 | A1 |
20140189677 | Curzi et al. | Jul 2014 | A1 |
20140201735 | Kannan et al. | Jul 2014 | A1 |
20140207912 | Thibeault | Jul 2014 | A1 |
20140215073 | Dow et al. | Jul 2014 | A1 |
20140245297 | Hackett | Aug 2014 | A1 |
20140279581 | Devereaux | Sep 2014 | A1 |
20140282615 | Cavage et al. | Sep 2014 | A1 |
20140289286 | Gusak | Sep 2014 | A1 |
20140304698 | Chigurapati et al. | Oct 2014 | A1 |
20140304815 | Maeda | Oct 2014 | A1 |
20140380085 | Rash et al. | Dec 2014 | A1 |
20150039891 | Ignatchenko et al. | Feb 2015 | A1 |
20150052258 | Johnson et al. | Feb 2015 | A1 |
20150074659 | Madsen et al. | Mar 2015 | A1 |
20150081885 | Thomas et al. | Mar 2015 | A1 |
20150106805 | Melander et al. | Apr 2015 | A1 |
20150120928 | Gummaraju et al. | Apr 2015 | A1 |
20150135287 | Medeiros et al. | May 2015 | A1 |
20150143381 | Chin et al. | May 2015 | A1 |
20150178110 | Li et al. | Jun 2015 | A1 |
20150186129 | Apte et al. | Jul 2015 | A1 |
20150235144 | Gusev et al. | Aug 2015 | A1 |
20150242225 | Muller et al. | Aug 2015 | A1 |
20150256621 | Noda et al. | Sep 2015 | A1 |
20150261578 | Greden et al. | Sep 2015 | A1 |
20150289220 | Kim et al. | Oct 2015 | A1 |
20150319160 | Ferguson et al. | Nov 2015 | A1 |
20150332048 | Mooring et al. | Nov 2015 | A1 |
20150350701 | Lemus et al. | Dec 2015 | A1 |
20150363181 | Alberti et al. | Dec 2015 | A1 |
20150371244 | Neuse et al. | Dec 2015 | A1 |
20150378764 | Sivasubramanian et al. | Dec 2015 | A1 |
20150378765 | Singh et al. | Dec 2015 | A1 |
20160012099 | Tuatini et al. | Jan 2016 | A1 |
20160072727 | Leafe et al. | Mar 2016 | A1 |
20160092250 | Wagner et al. | Mar 2016 | A1 |
20160098285 | Davis | Apr 2016 | A1 |
20160100036 | Lo | Apr 2016 | A1 |
20160224360 | Wagner et al. | Aug 2016 | A1 |
20160224785 | Wagner et al. | Aug 2016 | A1 |
20160239318 | Wagner | Aug 2016 | A1 |
20160285906 | Fine et al. | Sep 2016 | A1 |
20160294614 | Searle et al. | Oct 2016 | A1 |
20160299790 | Thompson | Oct 2016 | A1 |
20160301739 | Thompson | Oct 2016 | A1 |
20160364265 | Cao et al. | Dec 2016 | A1 |
20160371127 | Antony et al. | Dec 2016 | A1 |
20170093920 | Ducatel et al. | Mar 2017 | A1 |
20170116051 | Wagner et al. | Apr 2017 | A1 |
20170177391 | Wagner et al. | Jun 2017 | A1 |
20170177413 | Wisniewski et al. | Jun 2017 | A1 |
20170192804 | Wagner | Jul 2017 | A1 |
20170199766 | Wagner et al. | Jul 2017 | A1 |
20170206116 | Reque et al. | Jul 2017 | A1 |
20170286143 | Wagner et al. | Oct 2017 | A1 |
20170286156 | Wagner et al. | Oct 2017 | A1 |
20170371703 | Wagner et al. | Dec 2017 | A1 |
20170371706 | Wagner et al. | Dec 2017 | A1 |
20170371724 | Wagner et al. | Dec 2017 | A1 |
20180004553 | Wagner et al. | Jan 2018 | A1 |
20180004572 | Wagner et al. | Jan 2018 | A1 |
Number | Date | Country |
---|---|---|
2663052 | Nov 2013 | EP |
WO 2009137567 | Nov 2009 | WO |
WO 2015078394 | Jun 2015 | WO |
WO 2015108539 | Jul 2015 | WO |
WO 2016053950 | Apr 2016 | WO |
WO 2016053968 | Apr 2016 | WO |
WO 2016053973 | Apr 2016 | WO |
WO 2016090292 | Jun 2016 | WO |
WO 2016126731 | Aug 2016 | WO |
WO 2016164633 | Oct 2016 | WO |
WO 2016164638 | Oct 2016 | WO |
WO 2017112526 | Jun 2017 | WO |
WO 2017172440 | Oct 2017 | WO |
Entry |
---|
Anonymous: “Docker run reference”, Dec. 7, 2015, XP055350246, Retrieved from the Internet: URL:https://web.archive.org/web/20151207111702/https:/docs.docker.com/engine/reference/run/ [retrieved on Feb. 28, 2017]. |
Adapter Pattern, Wikipedia, https://en.wikipedia.org/w/index.php?title=Adapter_pattern&oldid=654971255, [retrieved May 26, 2016], 6 pages. |
Czajkowski, G., and L. Daynes, Multitasking Without Compromise: A Virtual Machine Evolution 47(4a):60-73, ACM SIGPLAN Notices—Supplemental Issue, Apr. 2012. |
Dombrowski, M., et al., Dynamic Monitor Allocation in the Java Virtual Machine, JTRES '13, Oct. 9-11, 2013, pp. 30-37. |
Espadas, J., et al., A Tenant-Based Resource Allocation Model for Scaling Software-as-a-Service Applications Over Cloud Computing Infrastructures, Future Generation Computer Systems, vol. 29, pp. 273-286, 2013. |
Nakajima, J., et al., Optimizing Virtual Machines Using Hybrid Virtualization, SAC '11, Mar. 21-25, 2011, TaiChung, Taiwan, pp. 573-578. |
Qian, H., and D. Medhi, et al., Estimating Optimal Cost of Allocating Virtualized Resources With Dynamic Demand, ITC 2011, Sep. 2011, pp. 320-321. |
Shim (computing), Wikipedia, https://en.wikipedia.org/w/index.php?title+Shim_(computing)&oldid+654971528, [retrieved on May 26, 2016], 2 pages. |
Vaghani, S.B., Virtual Machine File System, ACM SIGOPS Operating Systems Review 44(4):57-70, Dec. 2010. |
Vaquero, L., et al., Dynamically Scaling Applications in the cloud, ACM SIGCOMM Computer Communication Review 41(1):45-52, Jan. 2011. |
Zheng, C., and D. Thain, Integrating Containers into Workflows: A Case Study Using Makeflow, Work Queue, and Docker, VTDC '15, Jun. 15, 2015, Portland, Oregon, pp. 31-38. |
International Search Report and Written Opinion in PCT/US2015/052810 dated Dec. 17, 2015. |
International Preliminary Report on Patentability in PCT/US2015/052810 dated Apr. 4, 2017. |
International Search Report and Written Opinion in PCT/US2015/052838 dated Dec. 18, 2015. |
International Preliminary Report on Patentability in PCT/US2015/052838 dated Apr. 4, 2017. |
International Search Report and Written Opinion in PCT/US2015/052833 dated Jan. 13, 2016. |
International Preliminary Report on Patentability in PCT/US2015/052833 dated Apr. 4, 2017. |
International Search Report and Written Opinion in PCT/US2015/064071 dated Mar. 16, 2016. |
International Search Report and Written Opinion in PCT/US2016/016211 dated Apr. 13, 2016. |
International Search Report and Written Opinion in PCT/US2016/026514 dated Jun. 8, 2016. |
International Search Report and Written Opinion in PCT/US2016/026520 dated Jul. 5, 2016. |
International Search Report and Written Opinion in PCT/US2016/054774 dated Dec. 16, 2016. |
International Search Report and Written Opinion in PCT/US2016/066997 dated Mar. 20, 2017. |
Amazon, “AWS Lambda: Developer Guide”, Retrieved from the Internet, Jun. 26, 2016, URL : http://docs.aws.amazon.com/lambda/ latest/dg/lambda-dg.pdf. |
Ben-Yehuda et al., “Deconstructing Amazon EC2 Spot Instance Pricing”, ACM Transactions on Economics and Computation 1.3, 2013, 15 pages. |
Hoffman, Auto scaling your website with Amazon Web Services (AWS)—Part 2, Cardinalpath, Sep. 2015, 15 pages. |
International Preliminary Report on Patentability in PCT/US2015/064071 dated Jun. 6, 2017. |
International Preliminary Report on Patentability in PCT/US2016/016211 dated Aug. 17, 2017. |
International Preliminary Report on Patentability in PCT/US2016/026514 dated Oct. 10, 2017. |
International Preliminary Report on Patentability in PCT/US2016/026520 dated Oct. 10, 2017. |
International Search Report and Written Opinion in PCT/US/2017/023564 dated Jun. 6, 2017. |
International Search Report and Written Opinion in PCT/US2017/040054 dated Sep. 21, 2017. |
International Search Report and Written Opinion in PCT/US2017/039514 dated Oct. 10, 2017. |
Number | Date | Country | |
---|---|---|---|
20170090961 A1 | Mar 2017 | US |