Method and system for application load balancing

• US 7,454,458 B2
• Filed: 06/24/2002
• Issued: 11/18/2008
• Est. Priority Date: 06/24/2002
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: NTT Docomo Incorporated (Nippon Telegraph and Telephone Corporation)
• Inventors: Islam, Nayeem, Shoaib, Shahid
• Primary Examiner(s): Blair; Douglas B
• Application Number:
  US10/179,910
• Publication Number:
  US 20040003029A1
• Time in Patent Office: 2,339 Days
• Field of Search: 709/201, 709/204, 709/220, 709/224, 709/246, 709/203, 709/226, 706/3, 705/38, 703/14, 370/231, 714/47, 714/48
• US Class Current: 709/203
• CPC Class Codes: G06F 9/505 considering the load

Abstract

In one aspect of the invention, a method for load balancing an application among a plurality of computing devices coupled with at least one access network for communication between the devices is provided. The method comprises storing the application on a server device coupled with the access network. The method also comprises measuring a set of application attributes associated with the application, including at least one performance attribute for characterizing a user perceived performance of the application. The method further comprises issuing a request, from a client device coupled with the access network, for the application. Additionally, the method comprises provisioning execution of the application on the client or server device in response to the request based on the set of application attributes. The method further comprises executing the application on the client or server device in response to provisioning the execution of the application.

Claims

1. A method for load balancing an application among a plurality of computing devices communicably coupled with at least one access network for communication between the devices, the method comprising:

issuing a request, from a client device communicably coupled with said at least one access network, for said application;

monitoring a set of application attributes while executing said application, including measuring the set of application attributes associated with said application including at least one performance attribute for characterizing user perceived performance of said application based on one or more user interface events associated with a user interface of the application;

provisioning execution of said application on one of said client device and a server device in response to said request based on said set of application attributes, including determining whether to relocate said application from said server device to said client device based on said monitored set of application attributes while executing said application; and

executing said application on said one of said client and server devices based on provisioning execution of said application.

2. The method of claim 1 further comprising selecting a first access network for communication between said server device and client device based on said set of application attributes.

3. The method of claim 2 further comprising:

monitoring said set of application attributes while executing said application; and

determining whether to switch to a second access network for communication between said server device and client device based on said set of application attributes being monitored while executing said application.

4. The method of claim 1 wherein said at least one performance attribute comprises at least one parameter relating to latency for user interface events for said application, said latency defined based on at least one of server computation times and communication times.

5. The method of claim 4 wherein said at least one parameter relating to wait times comprises at least one of a mean of said wait times and a variance of said wait times.

6. The method of claim 5 wherein said server computation times comprise internal calculation times and data I/O times.

7. The method of claim 5 wherein said at least one performance attribute further comprises a total time for said application to run to completion.

8. The method of claim 1 wherein said at least one performance attribute is measured per application.

9. The method of claim 1 wherein said at least one performance attribute is measured per application per device.

10. The method of claim 1 wherein said at least one performance attribute is measured per application per device per user.

11. The method of claim 1 wherein said at least one performance attribute is measured per application per device per user per access network.

12. The method of claim 1 wherein said set of application attributes further includes at least one system attribute for characterizing performance of at least one of said client device, said server device and said at least one access network.

13. The method of claim 12 wherein the at least one system attribute comprises at least one of a parameter relating to a measure of utilization of a processor of said client device, a MIPS rating of said processor, memory size of said client device and an amount of persistent storage for said client device.

14. The method of claim 12 wherein the at least one system attribute comprises at least one of a parameter relating to a measure of utilization of a processor of said server device, a MIPS rating of said processor, memory size of said server device and an amount of persistent storage for said server device.

15. The method of claim 12 wherein the at least one system attribute comprises at least one of network bandwidth of said at least one access network, network latency of said at least one access network and network status of said at least one access network.

16. A system for load balancing an application being executed within at least one network, the system comprising one or more computer-readable storage media storing instructions which, when executed by one or more systems, cause the system to run a plurality of modules to load balance an application being executed within at least one network, the plurality of modules comprising:

a plurality of execution modules communicably coupled with said at least one network to provide different execution environments for said application, the different execution environments includes at least one server and at least one client;

at least one collection module coupled with said at least one network to monitor a set of application attributes while executing said application, the at least one collection module being operable to measure a set of application attributes associated with said application including at least one performance attribute for characterizing user perceived performance of said application based on one or more user interface events associated with a user interface of the application;

at least one policy module coupled with said at least one network to determine a first execution module that satisfies at least one policy for determining an execution environment of said application based on said application attributes; and

at least one program allocation module to allocate said application from a server to said first execution module, the first execution module being in a client.

17. The system of claim 16 further comprising at least one network allocation module to select an access network that satisfies at least one policy for determining a communication environment of said application based on said set of application attributes.

18. The system of claim 17 wherein said at least one performance attribute comprises at least one parameter relating to wait times for user interface events for said application, said wait times including at least one of server computation times and communication times.

19. The system of claim 18 wherein said at least one parameter relating to wait times comprises at least one of a mean of said wait times and a variance of said wait times.

20. The system of claim 19 wherein said server computation times comprise internal calculation times and data I/O times.

21. The system of claim 20 wherein said at least one performance attribute further comprises a total time for said application to run to completion.

22. The system of claim 16 wherein said at least one performance attribute is measured per application.

23. The system of claim 16 wherein said at least one performance attribute is measured per application per device.

24. The system of claim 16 wherein said at least one performance attribute is measured per application per device per user.

25. The system of claim 16 wherein said at least one performance attribute is measured per application per device per user per access network.

26. The system of claim 16 wherein said set of application attributes further includes at least one system attribute for characterizing performance of at least one of said client device, said server device and said at least one access network.

27. The system of claim 26 wherein the at least one system attribute comprises at least one of a parameter relating to a measure of utilization of a processor of said client device, a MIPS rating of said processor, memory size of said client device and an amount of persistent storage for said client device.

28. The system of claim 26 wherein the at least one system attribute comprises at least one of a parameter relating to a measure of utilization of a processor of said server device, a MIPS rating of said processor, memory size of said server device and an amount of persistent storage for said server device.

29. The system of claim 26 wherein the at least one system attribute comprises at least one of network bandwidth of said at least one access network, network latency of said at least one access network and network status of said at least one access network.

30. A system for load balancing an application among a plurality of computing devices communicably coupled with at least one access network for communication between the devices, the system comprising:

a client device communicably coupled with said at least one access network;

a server device;

means for issuing a request, from the client device communicably coupled with said at least one access network, for said application;

monitoring a set of application attributes while executing said application, including means for measuring the set of application attributes including at least one performance attribute for characterizing user perceived performance of said application based on one or more user interface events associated with a user interface of the application;

means for provisioning execution of said application on one of said server device and the client device in response to said request based on said set of application attributes, including means for determining whether to relocate said application from said server device to said client device during execution based on said monitored set of application attributes; and

means for executing said application on said one of said client and server devices provisioning execution of said application.

31. The system of claim 30 further comprising means for selecting a first access network based on said set of application attributes to communicate between said server device and client device.

32. The system of claim 31 further comprising:

means for monitoring said set of application attributes during execution of said application; and

means for determining whether to switch to a second access network during execution of said application based on said monitored set of application attributes to communicate between said server device and client device.

33. A method comprising:

monitoring a set of one or more application attributes associated with a mobile application program in a network comprising a plurality of nodes and an access network, the plurality of nodes including a mobile device, at least one of the application attributes characterizing user perceived performance of the application based on one or more user interface events associated with a user interface of the application; and

load balancing execution of the mobile application program based on the set of application attributes and a storage location of the mobile application program, wherein load balancing the application comprises

provisioning execution of the mobile application program on one of the plurality of nodes to achieve a level of user perceived performance of the mobile application program, wherein provisioning execution of the mobile application program comprises sending the mobile application program to a client device requesting the mobile application program if the set of application attributes is in a first state, and allowing a first server device that is storing the mobile application program to execute the mobile application program if the set of application attributes is in a second state, and

executing the application on the one node.

34. The method defined in claim 33 wherein the set of application attributes includes an attribute indicative of user perceived performance of the mobile application program.

35. The method defined in claim 33 wherein provisioning execution of the mobile application program comprises sending the mobile application program to a second server device for execution thereon if the set of application attributes is in a third state.

36. The method defined in claim 33 wherein the set of attributes characterizes one or more of interactivity of the application program and computation and data intensity of application program.

37. The method defined in claim 36 wherein the interactivity of the application program is based on interactions between previous invocations of the application program and a client device, including wait times associated with interactions with the application program.

38. The method defined in claim 33 wherein provision execution of the application program comprises a server determining whether to run the application program locally or on the mobile device based on one or more of the following:

the memory and processing capabilities of the mobile device and server nodes,

the load on each of the two mobile device and server nodes and network bandwidth and latency, and

the set of attributes related to the performance of the application program.

39. The method defined in claim 38 wherein the server determining whether to run the application program locally or on the mobile device comprises the server determining to run the application program on the mobile device if the application program is user-interactive and the mobile device has sufficient hardware resources to execute the application program.

40. The method defined in claim 38 wherein the server determining whether to run the application program locally or on the mobile device comprises the server determining to run the application program on the server if the application program is computationally intensive.

41. The method defined in claim 33 further comprising:

locating the application program in response to a request from the mobile device on a network,

creating an instance of the application program;

loading the instance of the application program into a memory.

42. The method defined in claim 33 further comprising the mobile device sending a request for the application program across a network, the request including an identifier to identify the application program, the processor utilization on the mobile device, the MIPS rating of the mobile device, the available memory and the persistent storage on the mobile device and any performance attributes of the application program if available.

43. An article of manufacture having one or more computer-readable storage media storing instructions thereon which, when executed by one or more systems, cause the one or more systems to perform a method comprising:

monitoring a set of one or more application attributes associated with a mobile application program in a network comprising a plurality of nodes and an access network, the plurality of nodes including a mobile device and a first server device, at least one of the application attributes characterizing user perceived performance of the application based on one or more user interface events associated with a user interface of the application; and

load balancing execution of the mobile application program based on the set of application attributes and a storage location of the mobile application program, wherein load balancing the application comprises

provisioning execution of the mobile application program on one of the plurality of nodes to achieve a level of user perceived performance of the mobile application program, wherein provisioning execution of the mobile application program comprises sending the mobile application program to a mobile device requesting the mobile application program if the set of application attributes is in a first state, and allowing the first server device that is storing the mobile application program to execute the mobile application program if the set of application attributes is in a second state, and

executing the application on the one node.