Non-intrusive gathering of code usage information to facilitate removing unused compiled code

Abstract

One embodiment of the present invention provides a system that gathers code usage information to facilitate removing compiled code that has not been recently used. This method operates in a mixed-mode system that supports execution of both compiled code and interpreter code. During operation, the system gathers usage information for compiled methods within an application while the application is executing. Next, the system identifies compiled methods to be removed based on this usage information, and removes identified compiled methods so that interpreter code is executed for the compiled methods instead of compiled code. In this way, the system frees up the memory space used to store the compiled methods.

Description

BACKGROUND

FIELD OF THE INVENTION

[0002] The present invention relates to compilers for computer systems. More specifically, the present invention relates to a method and an apparatus that non-intrusively gathers code usage information to facilitate removing compiled code in a mixed-mode system that supports execution of both compiled code and interpreter code.

RELATED ART

[0003] The exponential growth of the Internet has in part been fueled by the development of computer languages, such as the JAVA™ programming language distributed by Sun Microsystems, Inc. of Palo Alto, Calif. The JAVA programming language allows an application to be compiled into a module containing platform-independent bytecodes, which can be distributed across a network of many different computer systems. Any computer system possessing a corresponding platform-independent virtual machine, such as the JAVA virtual machine, is then able to execute the bytecodes. In this way, a single form of the application can be easily distributed to and executed by a large number of different computing platforms.

[0004] When an application is received in platform-independent form, it can be interpreted directly through an interpreter, or alternatively, it can be compiled into machine code for the native architecture of the computing platform. Machine code typically executes significantly faster than interpreter code. However, compiled code occupies considerably more space than interpreter code. Hence, the determination of whether or not to compile interpreter code depends on the relative importance of memory space to execution speed.

[0005] Some “mixed-mode” computer systems support execution of both compiled code and interpreter code. On a mixed-mode system, it is often desirable to eliminate a compiled method in order to free up memory space. However, existing mixed-mode systems can only unload a compiled method when the entire class associated with the compiled method is unloaded. This means that a large number of compiled methods associated with a class can potentially build up in memory before the class is unloaded. This is not a problem in larger computer systems, which have more memory to store compiled methods, and which can rely on the virtual memory system to migrate unused compiled methods to swap space in secondary storage.

[0006] However, constrained memory systems, such as pocket-sized computing devices, have limited memory space to accommodate compiled methods, and typically do not provide swap space in secondary storage for the virtual memory system.

[0007] Hence, what is needed is a method and an apparatus for removing an unused compiled method from memory without having to wait for the entire class associated with the compiled method to be unloaded.

SUMMARY

[0008] One embodiment of the present invention provides a system that gathers code usage information to facilitate removing compiled code that has not been recently used. This method operates in a mixed-mode system that supports execution of both compiled code and interpreter code. During operation, the system gathers usage information for compiled methods within an application while the application is executing. Next, the system identifies compiled methods to be removed based on this usage information, and removes identified compiled methods so that interpreter code is executed for the compiled methods instead of compiled code. In this way, the system frees up the memory space used to store the compiled methods.

[0009] In a variation on this embodiment, the system is part of a garbage collection mechanism that removes unreachable objects from the memory space of the application in addition to removing compiled methods.

[0010] In a variation on this embodiment, gathering the usage information involves keeping track of how many times each compiled method has been garbage collected without being executed. Furthermore, identifying the compiled methods to be removed involves identifying compiled methods that have been garbage collected more than a threshold number of times without being executed.

[0011] In a variation on this embodiment, the system keeps track of how many times a given compiled method has been garbage collected by replacing an instruction in the given compiled method with a trap instruction that causes the instruction to be restored to replace the trap instruction when the given method is executed after garbage collection. If the instruction has not been replaced since a preceding garbage collection operation, the system increments a counter associated with the trap instruction so that the counter indicates how many times the given method has been garbage collected without being executed.

[0012] In a further variation, the counter is stored in a pointer associated with the trap instruction so that additional memory space is not required to store the counter.

[0013] In a variation on this embodiment, if a given compiled method to be removed describes an activation record that is active on the execution stack, the system de-optimizes the activation record, which involves converting the activation record from being described by the given compiled method to being described by the interpreter.

[0014] In a variation on this embodiment, if a given compiled method to be removed describes an activation record that is active on the execution stack, the system does not remove the given compiled method, thereby avoiding the expense of de-optimizing the activation record.

[0015] In a variation on this embodiment, the system additionally determines a total amount of memory used by compiled methods, and then removes compiled methods if the total amount of memory used by compiled methods exceeds a threshold value.

[0016] In a variation on this embodiment, the system additionally determines a total amount of memory used by live user data, and then removes compiled methods if the total amount of memory used by live user data exceeds a threshold value, thereby freeing additional memory space to accommodate live user data.

BRIEF DESCRIPTION OF THE FIGURES

[0017] FIG. 1 illustrates a computing device in accordance with an embodiment of the present invention.

[0018] FIG. 2A illustrates how a compiled method is modified with a trap instruction in accordance with an embodiment of the present invention.

[0019] FIG. 2B illustrates code for a trap handler associated with the trap instruction in accordance with an embodiment of the present invention.

[0020] FIG. 3A is a flow chart illustrating the process of inserting a trap instruction into a compiled method in accordance with an embodiment of the present invention.

[0021] FIG. 3B is state diagram illustrating changes to a trap instruction in accordance with an embodiment of the present invention.

[0022] FIG. 4 is a flow chart illustrating the process of executing a trap instruction in accordance with an embodiment of the present invention.

[0023] FIG. 5 is a flow chart illustrating the process of removing compiled methods from memory in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

[0024] The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

[0025] The data structures and code described in this detailed description are typically stored on a computer readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs) and DVDs (digital versatile discs or digital video discs), and computer instruction signals embodied in a transmission medium (with or without a carrier wave upon which the signals are modulated). For example, the transmission medium may include a communications network, such as the Internet.

[0026] Computing Device

[0027] FIG. 1 illustrates a computing device 110 coupled to a development system 106 in accordance with an embodiment of the present invention. Development system 106 can generally include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a personal organizer, a device controller, or a computational engine within an appliance. Development system 106 contains development unit 108, which includes programming tools for developing platform-independent applications. This generally involves compiling an application from source code form into a platform-independent form, such as JAVA bytecodes.

[0028] Development system 106 is coupled to computing device 110 through a communication link 112. Computing device 110 can include any type of computing device or system including, but not limited to, a mainframe computer system, a server computer system, a personal computer system, a workstation, a laptop computer system, a pocket-sized computer system, a personal organizer or a device controller. Computing device 110 can also include a computing device that is embedded within another device, such as a pager, a cellular telephone, a television, an automobile, or an appliance.

[0029] Communication link 112 can include any type of permanent or temporary communication channel that may be used to transfer data from development system 106 to computing device 110. This can include, but is not limited to, a computer network such as an Ethernet, a wireless communication link or a telephone line.

[0030] Computing device 110 includes data store 114, for storing code and data. Computing device 110 also includes virtual machine 116 for processing platform-independent applications retrieved from data store 114.

[0031] During the development process, a class file 118 is created within development unit 108. Class file 118 contains components of a platform-independent application to be executed in computing device 110. For example, class file 118 may include methods and fields associated with an object-oriented class. Note that these methods are specified using platform-independent bytecodes 119.

[0032] Next, class file 118 is transferred from development unit 108, through communication link 112, into data store 114 within computing device 110. This allows virtual machine 116 to execute an application that makes use of components within class file 118. Note that virtual machine 116 can generally include any type of virtual machine that is capable of executing platform-independent code, such as the JAVA VIRTUAL MACHINE™ developed by SUN Microsystems, Inc. of Palo Alto Calif. (Sun, Sun Microsystems, Java and Java Virtual Machine are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.)

[0033] Virtual machine 116 includes object heap 122 for storing objects that are manipulated by code executing on virtual machine 116. Object heap 122 also stores compiled methods 123.

[0034] Virtual machine 116 also includes an interpreter 120, which interprets platform-independent bytecodes 119 retrieved from data store 114 to facilitate program execution. During operation, interpreter 120 generally translates one bytecode at a time as bytecodes 119 are continuously read into interpreter 120.

[0035] Alternatively, virtual machine can use compiler 121 to compile methods from bytecode form into machine code form to produce compiled methods 123, which are stored in object heap 122.

[0036] Note that the interpreter code equivalent of a compiled method can be retrieved again at any time from data store 114. Virtual machine 116 includes a runtime system 124. Runtime system 124 maintains state information for threads 130-131. This state information includes execution stacks 140-141, respectively. Execution stacks 140-141 store activation records for methods being executed by threads 130-131, respectively.

[0037] Runtime system 124 can either execute code that is received from interpreter 120, or compiled methods 123 received from object heap 122. When a method is invoked by virtual machine 116, the system first determines if the method is to be invoked as an interpreted method. If so, runtime system 124 obtains the method from interpreter 120.

[0038] If, on the other hand, the system determines that the method is to be invoked as a compiled method, runtime system 124 activates compiler 121, which generates machine code instructions from the bytecodes. These machine code instructions are subsequently executed by runtime system 124.

[0039] Virtual machine also includes garbage collector 150, which periodically reclaims unused storage from object heap 122.

[0040] Trap Instruction

[0041] FIG. 2A illustrates how a compiled method 201 is modified with a trap instruction in accordance with an embodiment of the present invention. The left-hand side of FIG. 2A illustrates a compiled method 201, which is stored as an object within object heap 122. Hence, compiled method 201 includes an object header 202 as well as a set of instructions 211-213.

[0042] As is illustrated on the right-hand side of FIG. 3, compiled method 201 is modified by first saving instruction 211 from the entry point of compiled method 201 to temporary storage 204. Second, a trap instruction to location AGE—0 is stored in place of instruction 211 at the entry point of the compiled method.

[0043] FIG. 2B illustrates code for a trap handler associated with the trap instruction in accordance with an embodiment of the present invention. This code includes a number of “No Operation” (NOP) instructions followed by an instruction that restores instruction 211 from temporary storage 204 back to its original location at the entry point of compiled method 201.

[0044] Hence, when compiled method 201 is subsequently invoked for the first time after the trap instruction is inserted, compiled method 201 is restored back to its original form. Note that subsequent invocations of compiled method 201 do not perform the trap instruction, and hence do not suffer any performance penalty.

[0045] Process of Inserting a Trap Instruction

[0046] FIG. 3A is a flow chart illustrating the process of inserting a trap instruction into a compiled method 201 in accordance with an embodiment of the present invention. In one embodiment of the present invention, this process takes place during a garbage collection operation that removes unused objects from object heap 122.

[0047] When a compiled method 201 is encountered, the system first determines if a trap instruction has been installed into the compiled method 201 (step 302). If not, the system saves the original code (instruction 211) from the entry point of compiled method 201 in temporary storage 204 (step 304). The system then stores a trap instruction “TRAP AGE—0” to the entry point of compiled method 201 (step 306).

[0048] If in step 302 the system determines that a trap instruction has been installed, the system increments the pointer associated with the trap instruction (step 308). In this way, the pointer associated with the trap instruction keeps track of how many times the compiled method has been garbage collected without being executed. This allows the system to determine which compiled methods have been least recently used. A state diagram illustrating changes to the trap instruction appears in FIG. 3B.

[0049] Note that by keeping track of this information in the pointer associated with the trap instruction, no additional memory space is needed to keep track of this information. Also note that an upper limit can be established on the number of times this pointer can be incremented to prevent the trap instruction from trapping to an undefined memory location.

[0050] Process of Executing a Trap Instruction

[0051] FIG. 4 is a flow chart illustrating the process of executing a trap instruction in accordance with an embodiment of the present invention. As was mentioned above, execution of the trap instruction restores instruction 211 to its original location at the entry point of compiled method 201 (step 402), so that subsequent invocations of compiled method 201 suffer no performance penalty. Hence, the performance penalty for collecting this method usage information is simply the cost of restoring the original code the first time the compiled method is executed after garbage collection.

[0052] Process of Removing Compiled Methods

[0053] FIG. 5 is a flow chart illustrating the process of removing compiled methods from memory in accordance with an embodiment of the present invention. During a periodic garbage collection operation, garbage collector 150 determines whether to remove compiled code from object heap 122 (step 502). This can happen for a number of reasons. For example, the amount of compiled code can exceed a total amount of memory allowed for compiled code, or the amount of live user data can grow to a point where it is desirable to trade compiled code for live user data.

[0054] If the system determines that no compiled code needs be removed, garbage collector 150 does not remove compiled code, and only performs normal garbage collection operations to remove unreachable objects from object heap 122.

[0055] Otherwise, if the system determines that compiled code needs to be removed, the system removes compiled methods with the oldest trap instructions (step 504). Note that during the garbage collection process, the system scans through all reachable objects within object heap 122. Hence, it is a simple matter to check the trap age of each compiled method and to remove compiled methods having a trap age that exceeds a threshold value.

[0056] Also note that if a compiled method to be removed describes an activation record that is active on the execution stack, the system may choose to de-optimize the activation record so that the activation record is described by the interpreter instead of by the compiled method (step 506). Alternatively, the system may simply choose not to remove a compiled method with an activation record that is active on the execution stack.

[0057] Note that when a method is compiled, the structure of the associated activation record on its execution stack is generally changed into an “optimized” form. Hence, when a compiled method is removed, and the compiled method describes an activation record that is active on the execution stack, the corresponding activation record must be de-optimized. This can be accomplished through a process described in U.S. Pat. No. 5,933,635, entitled, “Method and Apparatus for Dynamically Deoptimizing Compiled Methods,” by inventors Urs Holze and Lars Bak, filed on Oct. 6, 1997 and issued on Aug. 3, 1999.

[0058] The foregoing descriptions of embodiments of the present invention have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.

Claims

1. A method for gathering code usage information to facilitate removing compiled code that has not been recently used, wherein the method operates in a mixed-mode system that supports execution of both compiled code and interpreter code, the method comprising: gathering usage information for compiled methods within an application while the application is executing; identifying compiled methods to be removed based on the usage information; and removing the identified compiled methods so that interpreter code is executed for the compiled methods instead of compiled code; whereby removing the compiled methods frees up the memory space used to store the compiled methods.

2. The method of claim 1, wherein the method operates during a garbage collection operation that removes unreachable objects from the memory space of the application in addition to removing compiled methods.

3. The method of claim 2, wherein gathering the usage information involves keeping track of how many times each method has been garbage collected without being executed; and wherein identifying the compiled methods to be removed involves identifying compiled methods that have been garbage collected more than a threshold number of times without being executed.

4. The method of claim 3, wherein keeping track of how many times a given method has been executed involves: replacing an instruction in the given method with a trap instruction that causes the instruction to be restored to replace the trap instruction when the given method is executed after garbage collection; and if the instruction has not been replaced since a preceding garbage collection operation, incrementing a counter associated with the trap instruction so that the counter indicates how many times the given method has been garbage collected without being executed.

5. The method of claim 4, wherein the counter is stored in a pointer associated with the trap instruction so that additional memory space is not required to store the counter.

6. The method of claim 1, wherein if a given compiled method to be removed describes an activation record that is active on the execution stack, the method further comprises de-optimizing the activation record; wherein de-optimizing the activation record involves converting the activation record from being described by the given compiled method to being described by the interpreter.

7. The method of claim 1, wherein if a given compiled method to be removed describes an activation record that is active on the execution stack, the method does not remove the given compiled method, thereby avoiding the expense of de-optimizing the activation record.

8. The method of claim 1, wherein the method further comprises: determining a total amount of memory used by compiled methods; and removing compiled methods if the total amount of memory used by compiled methods exceeds a threshold value.

9. The method of claim 1, wherein the method further comprises: determining a total amount of memory used by live user data; and removing compiled methods if the total amount of memory used by live user data exceeds a threshold value, thereby freeing additional memory space to accommodate live user data.

10. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for gathering code usage information to facilitate removing compiled code that has not been recently used, wherein the method operates in a mixed-mode system that supports execution of both compiled code and interpreter code, the method comprising: gathering usage information for compiled methods within an application while the application is executing; identifying compiled methods to be removed based on the usage information; and removing the identified compiled methods so that interpreter code is executed for the compiled methods instead of compiled code; whereby removing the compiled methods frees up the memory space used to store the compiled methods.

11. The computer-readable storage medium of claim 10, wherein the method operates during a garbage collection operation that removes unreachable objects from the memory space of the application in addition to removing compiled methods.

12. The computer-readable storage medium of claim 11, wherein gathering the usage information involves keeping track of how many times each method has been garbage collected without being executed; and wherein identifying the compiled methods to be removed involves identifying compiled methods that have been garbage collected more than a threshold number of times without being executed.

13. The computer-readable storage medium of claim 12, wherein keeping track of how many times a given method has been executed involves: replacing an instruction in the given method with a trap instruction that causes the instruction to be restored to replace the trap instruction when the given method is executed after garbage collection; and if the instruction has not been replaced since a preceding garbage collection operation, incrementing a counter associated with the trap instruction so that the counter indicates how many times the given method has been garbage collected without being executed.

14. The computer-readable storage medium of claim 13, wherein the counter is stored in a pointer associated with the trap instruction so that additional memory space is not required to store the counter.

15. The computer-readable storage medium of claim 10, wherein if a given compiled method to be removed describes an activation record that is active on the execution stack, the method further comprises de-optimizing the activation record; wherein de-optimizing the activation record involves converting the activation record from being described by the given compiled method to being described by the interpreter.

16. The computer-readable storage medium of claim 10, wherein if a given compiled method to be removed describes an activation record that is active on the execution stack, the method does not remove the given compiled method, thereby avoiding the expense of de-optimizing the activation record.

17. The computer-readable storage medium of claim 10, wherein the method further comprises: determining a total amount of memory used by compiled methods; and removing compiled methods if the total amount of memory used by compiled methods exceeds a threshold value.

18. The computer-readable storage medium of claim 10, wherein the method further comprises: determining a total amount of memory used by live user data; and removing compiled methods if the total amount of memory used by live user data exceeds a threshold value, thereby freeing additional memory space to accommodate live user data.

19. An apparatus for gathering code usage information to facilitate removing compiled code that has not been recently used, wherein the apparatus operates in a mixed-mode system that supports execution of both compiled code and interpreter code, the apparatus comprising: a monitoring mechanism that is configured to gather usage information for compiled methods within an application while the application is executing; and a method removal mechanism that is configured to, identify compiled methods to be removed based on the usage information, and to remove the identified compiled methods so that interpreter code is executed for the compiled methods instead of compiled code, whereby removing the compiled methods frees up the memory space used to store the compiled methods.

20. The apparatus of claim 19, wherein the apparatus is part of a garbage collection mechanism that removes unreachable objects from the memory space of the application in addition to removing compiled methods.

21. The apparatus of claim 20, wherein the monitoring mechanism is configured to keep track of how many times each method has been garbage collected without being executed; and wherein the method removal mechanism is configured to identify compiled methods that have been garbage collected more than a threshold number of times without being executed.

22. The apparatus of claim 21, wherein the monitoring mechanism is configured to: replace an instruction in a given method with a trap instruction that causes the instruction to be restored to replace the trap instruction when the given method is executed after garbage collection; and if the instruction has not been replaced since a preceding garbage collection operation, to increment a counter associated with the trap instruction so that the counter indicates how many times the given method has been garbage collected without being executed.

23. The apparatus of claim 22, wherein the counter is stored in a pointer associated with the trap instruction so that additional memory space is not required to store the counter.

24. The apparatus of claim 19, further comprising a de-optimization mechanism; wherein if a given compiled method to be removed describes an activation record that is active on the execution stack, the de-optimization mechanism is configured to de-optimize the activation record; wherein de-optimizing the activation record involves converting the activation record from being described by the given compiled method to being described by the interpreter.

25. The apparatus of claim 19, wherein if a given compiled method to be removed describes an activation record that is active on the execution stack, the method removal mechanism is configured not to remove the given compiled method, thereby avoiding the expense of de-optimizing the activation record.

26. The apparatus of claim 19, wherein the method removal mechanism is additionally configured to: determine a total amount of memory used by compiled methods; and to remove compiled methods if the total amount of memory used by compiled methods exceeds a threshold value.

27. The apparatus of claim 19, wherein the method removal mechanism is additionally configured to: determine a total amount of memory used by live user data; and to remove compiled methods if the total amount of memory used by live user data exceeds a threshold value, thereby freeing additional memory space to accommodate live user data.