OVERCOMING COMPILATION BUFFER OVERLOADS IN VIRTUAL MACHINES

• US 20080005403A1
• Filed: 06/29/2006
• Published: 01/03/2008
• Est. Priority Date: 06/29/2006
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Di Flora, Cristiano
• Application Number:
  US11/427,586
• Publication Number:
  US 20080005403A1
• Time in Patent Office: Days
• US Class Current: 710/56
• CPC Class Codes: G06F 9/45516 Runtime code conversion or optimisation

Abstract

Apparatuses and methods that allow a virtual machine on a device to overcome method cache overloads in dynamic just-in-time (JIT) compilation are disclosed. The apparatuses and methods dynamically adjust the size of a buffer caching compiled native code according to the effective run-time behavior of running applications on the device. Modules in the device monitor the method calls associated with the buffer to detect non-performance-critical and performance-critical overload conditions. The size of the buffer is increase, decreased, or not changed accordingly.

Claims

1. A device configured to dynamically adjust size of a buffer, comprising:

a memory unit, comprising;

compiler module including a buffer;

buffer monitor module that monitors for an overload condition in the compiler module;

overload detector module that determines type of overload condition in the compiler module based at least in part on information from the buffer monitor module; and

buffer shaper module that dynamically adjusts size of the buffer in the compiler module based at least in part on information from the overload detector module; and

a processor coupled to the memory unit and programmed with at least the compiler module, the buffer monitor module, the overload detector module, and the buffer shaper module.

2. The device of claim 1, wherein the buffer monitor module outputs an indication of overload condition to the overload detector module, wherein the overload detector module outputs an indication of overload condition type to the buffer shaper module, and wherein overload threshold values are input into the buffer monitor module.

3. The device of claim 1, wherein the compiler module comprises a just-in-time compiler, and wherein at least part of the buffer is stored in a dynamic heap memory.

4. The device of claim 1, wherein the buffer monitor module comprises a counter, and wherein the buffer monitor module intercepts particular method calls associated with the buffer and increments the counter.

5. The device of claim 4, wherein the buffer comprises a method-compilation cache, and wherein the particular method calls intercepted by the buffer monitor module comprise a request to add a method to the method-compilation cache and a request to remove a method from the method-compilation cache.

6. The device of claim 1, wherein the overload detector module outputs an indication of a non-performance-critical overload condition to the buffer shaper module if the overload detector module detects a non-performance-critical overload condition, and wherein the overload detector module outputs an indication of a performance-critical overload condition to the buffer shaper module if the overload detector module detects a performance-critical overload condition.

7. The device of claim 1, wherein the overload detector module comprises a count-and-threshold mechanism that detects a non-performance-critical overload condition in the compiler module.

8. The device of claim 7, wherein the count-and-threshold mechanisms comprises an alpha-count mechanism.

9. The device of claim 1, wherein the size of the buffer in the compiler module is increased if the information from the overload detector module indicates a performance-critical overload condition in the compiler module.

10. The device of claim 1, wherein the size of the buffer in the compiler module is decreased if the information from the overload detector module indicates none of a performance-critical overload condition or a non-performance-critical overload condition in the compiler module.

11. The device of claim 1, wherein the device is located in a mobile terminal.

12. A method for adjusting size of a buffer in a compiler module, comprising:

(a) monitoring particular method calls associated with the buffer in the compiler module occurring over a particular period of time to identify an overload condition, wherein the particular method calls monitored comprise a request to add information to the buffer and a request to remove information from the buffer;

(b) detecting a type of overload condition in the compiler module using a count-and-threshold mechanism that is capable of detecting a plurality of types of overload conditions, wherein the types of overload conditions comprise a non-performance-critical overload condition, a performance-critical overload condition, and a no overload condition;

(c) generating an indication corresponding to the type of overload condition in the compiler module; and

(d) decreasing size of the buffer if the indication corresponds to the no overload condition.

13. The method of claim 12, comprising:

(e) increasing size of the buffer if the indication corresponds to the performance-critical overload condition; and

(f) not changing size of the buffer if the indication corresponds to the non-performance-critical overload condition.

14. The method of claim 12, wherein (a) uses a predetermined overload threshold value to identify an overload condition.

15. The method of claim 12, wherein the count-and-threshold mechanism comprises an alpha-count mechanism using a predetermined alpha threshold value.

16. The method of claim 15, wherein (b) comprises:

calculating a first alpha value for a first particular period of time;

calculating a second alpha value for a second particular period of time, wherein the first alpha value is used in calculating the second alpha value; and

comparing the second alpha value to the predetermined alpha threshold value to detect the type of overload condition in the compiler module.

17. The method of claim 12, wherein the compiler module comprises a just-in-time compiler, wherein the buffer comprises a method-compilation cache stored in a dynamic heap memory.

18. A computer-readable medium storing computer-executable instructions for performing a method comprising:

(a) monitoring particular method calls associated with a buffer in a compiler module to identify an overload condition;

(b) detecting a type of overload condition in the compiler module;

(c) increasing size of the buffer if the type of overload condition in the compiler module corresponds to a performance-critical overload condition;

(d) decreasing size of the buffer if the type of overload condition in the compiler module corresponds to a no overload condition; and

(e) not changing size of the buffer if the type of overload condition in the compiler module corresponds to the non-performance-critical overload condition.

19. The computer-readable medium of claim 18, wherein (b) uses an alpha-count mechanism to detect the type of overload condition in the compiler module.

20. The computer-readable medium of claim 18, wherein the buffer comprises a method-compilation cache, and wherein the particular method calls monitored comprise a request to add a method to the buffer and a request to remove a method from the buffer.

21. A method of dynamically allocating size of a buffer in a mobile terminal, comprising:

(a) monitoring an effective run-time behavior of an application running on the mobile terminal; and

(b) adjusting the size of the buffer in the mobile terminal based on (a), wherein the buffer caches compiled native machine code.

22. The method of claim 21, wherein the effective run-time behavior comprises a request to add information to the buffer and a request to remove information from the buffer, wherein the buffer comprises a method-compilation cache.

23. The method of claim 21, wherein (a) comprises:

detecting a type of overload condition in the buffer using a count-and-threshold mechanism;

24. The method of claim 23, wherein (b) comprises:

increasing the size of the buffer in the mobile terminal if the type of overload condition corresponds to the performance-critical overload condition;

decreasing the size of the buffer in the mobile terminal if the type of overload condition corresponds to the no overload condition; and

not changing the size of the buffer in the mobile terminal if the type of overload condition corresponds to the non-performance-critical overload condition.

25. A device configured to dynamically adjust size of a buffer, comprising:

a memory unit, comprising;

compiler module including a buffer;

means for monitoring for an overload condition in the compiler module;

means for determining type of overload condition in the compiler module based at least in part on information from the buffer monitor module; and

means for dynamically adjusting size of the buffer in the compiler module based at least in part on information from the overload detector module; and

a processor coupled to the memory unit and programmed with at least the compiler module, the buffer monitor module, the overload detector module, and the buffer shaper module.

26. The device of claim 25, wherein the compiler module comprises a just-in-time compiler, and wherein at least part of the buffer is stored in a dynamic heap memory.

27. The device of claim 25, wherein the means for determining type of overload condition comprises an alpha-count mechanism that detects a non-performance-critical overload condition in the compiler module.