AUTOMATIC VIRTUAL MACHINE RESIZING TO OPTIMIZE RESOURCE AVAILABILITY

• US 20150355927A1
• Filed: 06/04/2014
• Published: 12/10/2015
• Est. Priority Date: 06/04/2014
• Status: Abandoned Application

• Current Assignee: Excalibur IP, LLC (Acacia Research Corporation)
• Original Assignee: Yahoo! Inc. (Apollo Global Management, Inc.)
• Inventors: Budzinski, Jeff
• Application Number:
  US14/296,341
• Publication Number:
  US 20150355927A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

In one embodiment, a configuration associated with an application may be ascertained, where the configuration indicates a number of instances and a first instance type. Requests associated with the application may be routed among two or more sets of instances, where each of the two or more sets of instances have a different, corresponding instance type of two or more instance types including the first instance type. Metrics associated with the routing of requests to each of the two or more sets of instances may be obtained. The metrics may be analyzed to identify an optimal instance type for the application. Further requests associated with the application may be routed to a set of the number of instances having the optimal instance type.

Claims

1. A method, comprising:

ascertaining a configuration associated with an application, the configuration indicating a number of instances and a first instance type;

facilitating launching of two or more sets of instances in association with the application, each of the two or more sets of instances having a different, corresponding instance type of two or more instance types including the first instance type and one or more additional instance types;

obtaining metrics associated with routing of requests to each of the two or more sets of instances;

analyzing the metrics to identify an optimal instance type for the application; and

facilitating instance resizing according to the optimal instance type.

2. The method as recited in claim 1, wherein facilitating instance resizing comprises:

eliminating each set of the two or more sets of instances not having the optimal instance type and causing one or more additional instances having the optimal instance type to launch such that the number of instances having the optimal instance type are running.

3. The method of claim 1, wherein the two or more instance types include at least one of:

at least one instance type that is smaller than the first instance type or at least one instance type that is larger than the first instance type.

4. The method of claim 1, wherein analyzing metrics associated with routing requests to each of the two or more sets of instances to identify an optimal instance type for the application comprises:

ascertaining a first set of metrics associated with a first set of the two or more sets of instances, the first set of instances corresponding to the first instance type; and

ascertaining one or more additional sets of metrics associated with each of the remaining sets of the two or more sets of instances, the remaining sets of instances corresponding to the one or more additional instance types; and

determining whether an instance type of the one or more additional instance types has a set of metrics that, when compared to the first set of metrics, provides a performance differential that is an acceptable amount according to a threshold.

5. The method of claim 1, wherein analyzing metrics associated with routing requests to each of the two or more sets of instances to identify an optimal instance type for the application comprises:

ascertaining a first set of metrics associated with a first set of the two or more sets of instances, the first set of instances corresponding to the first instance type; and

ascertaining one or more additional sets of metrics associated with each of the remaining sets of the two or more sets of instances, the remaining sets of instances corresponding to the one or more additional instance types; and

identifying a smallest instance type of the one or more additional instance types for which a set of metrics, when compared to the first set of metrics, provides a performance differential that is an acceptable amount according to a threshold.

6. The method of claim 1, wherein analyzing metrics associated with routing requests to each of the two or more sets of instances to identify an optimal instance type for the application comprises:

ascertaining a first set of metrics associated with a first set of the two or more sets of instances, the first set of instances corresponding to the first instance type; and

ascertaining one or more additional sets of metrics associated with each of the remaining sets of the two or more sets of instances, the remaining sets of instances corresponding to the one or more additional instance types; and

identifying a smallest instance type of the one or more additional instance types for which a set of metrics, when compared to the set of metrics associated with the first instance type, provides a performance improvement that is greater than a first threshold or a performance degradation that is less than a second threshold.

7. The method of claim 1, wherein the metrics indicate a latency associated with processing the corresponding requests or a user response to the latency.

8. An apparatus, comprising:

a processor; and

a memory, at least one of the processor or the memory being configured for;

ascertaining a configuration associated with an application, the configuration indicating a number of instances and a first instance type;

facilitating launching of two or more sets of instances in association with the application, each of the two or more sets of instances having a different, corresponding instance type of two or more instance types including the first instance type;

obtaining metrics associated with routing of requests to each of the two or more sets of instances; and

analyzing the metrics to identify an optimal instance type for the application.

9. The apparatus of claim 8, at least one of the processor or the memory being configured for performing operations, further comprising:

automatically performing instance resizing according to the optimal instance type such that a set of the number of instances having the optimal instance type is associated with the application.

10. The apparatus of claim 9, at least one of the processor or the memory being configured for performing operations, further comprising:

facilitating instance resizing according to the optimal instance type.

11. The apparatus of claim 8, at least one of the processor or the memory being configured for performing operations, further comprising:

terminating each set of the two or more sets of instances not having the optimal instance type and causing an additional set of instances having the optimal instance type to launch such that the number of instances having the optimal instance type are running.

12. The apparatus of claim 8, at least one of the processor or the memory being configured for performing operations, further comprising:

providing information indicating the optimal instance type;

receiving input pertaining to the information; and

facilitating instance resizing according to the input.

13. The apparatus of claim 8, wherein the two or more instance types comprise at least one of an instance type that is smaller than the first instance type or an instance type that is larger than the first instance type.

14. The apparatus of claim 8, wherein the metrics indicate a latency associated with processing the corresponding requests or a user response to the latency.

15. A system, comprising:

means for ascertaining a configuration associated with an application, the configuration indicating a number of instances and a first instance type;

means for facilitating launching of two or more sets of instances in association with the application, each of the two or more sets of instances having a different, corresponding instance type of two or more instance types including the first instance type;

means for obtaining metrics associated with routing of requests to each of the two or more sets of instances; and

means for analyzing the metrics to identify an optimal instance type for the application.

16. The system of claim 15, further comprising:

means for facilitating instance resizing according to the optimal instance type such that a set of the number of instances having the optimal instance type is associated with the application.

17. The system of claim 15, wherein the two or more instance types include at least one of an instance type that is smaller than the first instance type or an instance type that is larger than the first instance type.

18. The system of claim 15, further comprising:

means for terminating each set of the two or more sets of instances not having the optimal instance type; and

means for causing an additional set of instances having the optimal instance type to launch such that the number of instances having the optimal instance type are running.

19. The system of claim 15, wherein the metrics indicate a latency associated with processing the corresponding requests or a user response to the latency.

20. The system of claim 15, further comprising:

means for providing information indicating the optimal instance type;

means for receiving input pertaining to the information; and

means for facilitating instance resizing according to the input.