|Número da publicação||US6970893 B2|
|Tipo de publicação||Concessão|
|Número do pedido||US 10/162,308|
|Data de publicação||29 nov. 2005|
|Data de depósito||4 jun. 2002|
|Data da prioridade||27 out. 2000|
|Status da taxa||Pagas|
|Também publicado como||US7650370, US20030131012, US20050256913|
|Número da publicação||10162308, 162308, US 6970893 B2, US 6970893B2, US-B2-6970893, US6970893 B2, US6970893B2|
|Cessionário original||Bea Systems, Inc.|
|Exportar citação||BiBTeX, EndNote, RefMan|
|Citações de patente (12), Citações de não patente (2), Citada por (8), Classificações (7), Eventos legais (7)|
|Links externos: USPTO, Cessão do USPTO, Espacenet|
This application is a continuation-in-part of “SYSTEM AND METHOD FOR REGENERATION OF METHODS AND GARBAGE COLLECTION OF UNUSED METHODS”. This application is a Continuation-in-part of U.S. application Ser. No. 10/111,566 filed Oct. 31, 2002 which is the National Stage of International Application No. PCT/SE00/02096 filed Oct. 27, 2000, and also claims benefit of 60/368,920 Mar. 29, 2002. All of the above applications are incorporated herein by reference.
The invention relates to a method of improving the effectiveness of a data processing application when using a virtual machine, where the program includes many methods.
In a computer system, the ability to control the allocation of memory resources is vital to the successful operation and scalability of the computer system as a whole. Software applications run more efficiently in environments in which steps are taken to proactively manage available memory resources to ensure that only those entities that are currently being used are stored in memory, while little-used entities are cleanly removed. Such memory management techniques have commonly been applied to object management, including the Java language, and other object-oriented environments. Many memory management techniques can be designed to be automatic, or to allow a developer control over the allocation. Java and other dynamic program languages include an automatic memory management. This means that the programmer need not keep an account of those parts of the memory that are used. The virtual machine carries out a so-called garbage collection from time to time, meaning, in principle, that the virtual machine scans the entire memory and finds which objects have been stored in the memory and which objects the program can no longer address. These parts of the memory are returned for later use.
Java also includes a built-in thread management system for supporting or simulating the simultaneous processing of two or more processes/activities. The thread management system is responsible for allocating memory resources to each thread, and deciding which threads shall be run, and which threads shall be made passive.
However, in order to further increase effectiveness and place occupied memory space at the disposal of the program, it is not sufficient to solely optimize the memory with respect to the objects. Additional mechanisms are required when the program includes many methods, to better optimize the arrangement of methods within the memory space.
The present invention relates to a system and method of improving the effectiveness of a data processing application when using a virtual machine, where the program includes many methods, i.e. program sections, that are stored in the memory of the computer used, and where garbage collecting is used by said program, wherein the inventive method is characterized by a first step in which all so-called thread stacks are analyzed with respect to methods required thereby; a second step in which each of the methods required is caused to be regenerated where occurrent references to a method are replaced with reference to regenerated methods prior to the regeneration of a method; and by a third step in which all non-regenerated methods are erased, wherein the corresponding memory space is placed at the disposal of said program.
More specifically, the invention is concerned with increasing the data processing rate in virtual machines, and then particularly with respect to the Java program language.
The invention is not restricted to Java, but can be applied with many program languages, although the invention is described below primarily with reference to Java.
The system and methods provided by the invention are intended for use with adaptive optimization of a program. In adaptive optimization, the program is restructured and different parts of the program are optimized as the program is run. Increased data processing capacity results in the rapid creation of new memory sites, since the longer the program is run, the more memory space is required. The invention provides a mechanism to best utilize this memory space.
In one embodiment the invention comprises a process for deciding which methods (and in some cases which versions of the methods thereof) should be kept in memory, and optimizing the distribution of those methods within the memory space of a computer system or virtual machine, comprising the steps of: determining a selection of methods to be regenerated; creating regenerated methods, and replacing references to each method with references to the regenerated method; and, erasing all non-regenerated methods and releasing the memory space occupied by those non-regenerated methods. The above step of determining includes analyzing thread stacks associated with each method.
As described above, Java and other dynamic program languages include an automatic memory management. The virtual machine carries out a so-called garbage collection from time to time, meaning, in principle, that the virtual machine scans the entire memory and finds which objects have been stored in the memory and which the program can no longer address. These parts of the memory are returned for later use. Java also includes a built-in thread management system. In such a system, threads form the core entities upon which applications execute and communicate with the server. Thus, Java incorporates a system for supporting or simulating the simultaneous processing of two or more activities/processes.
However, in order to further increase effectiveness and to place occupied memory space at the disposal of the program, it is not sufficient to solely optimize the memory with respect to the objects. Additional mechanisms are required when the program includes many methods, to better control the distribution of methods within the memory space, and to decide which methods (and in some cases which versions of the methods) should actually be kept in memory. This leads to a more optimal arrangement of methods within the memory space of a computer system or virtual machine. The present invention addresses this problem.
The present invention thus relates to a method of improving the effectiveness of a data processing application when using a virtual machine, where the program includes many methods, i.e. program sections, that are stored in the memory of the computer used, and where garbage collecting is used by said program. In one embodiment, the method is characterized by a first step in which all so-called thread stacks are analyzed with respect to methods required thereby; a second step in which each of the methods required is caused to be regenerated where occurrent references to a method are replaced with reference to regenerated methods prior to the regeneration of a method; and by a third step in which all non-regenerated methods are erased, wherein the corresponding memory space is placed at the disposal of said program.
The present invention will now be described in more detail partly with reference to an exemplifying embodiment of the invention shown on to the accompanying drawings.
The present invention thus relates to a system and method of improving the effectiveness of a data processing application when using a virtual machine, wherein the program includes a large number of methods, i.e. program sections, that are stored in the memory of the computer used, and wherein a garbage collecting process is used by the program.
It is previously known to garbage collect objects and therewith erase objects that are no longer in current use by thereby placing corresponding memory capacity at the disposal of the system.
In large systems, many methods, i.e. program sections, are used one or a few times, or methods are applied for a short period of time and then left unused.
In the case of Java and corresponding programs, new methods are loaded and old methods left unused.
Furthermore, adaptive optimization results in the optimization and re-optimization of methods placed in the memory, where old methods are left unused.
When performing optimizations that select the most appropriate locking mechanisms, or when the garbage collector is adaptively changed, it is necessary to replace all of the previous methods that utilized the older mechanisms with new methods utilizing the new mechanisms.
Generally described, the invention first identifies methods to be regenerated. According to an embodiment of the invention, all so called thread stacks are analyzed with respect to the methods required, in a first step of the inventive method. In a second step, each of the methods required is regenerated, where occurrent references to a method are replaced with references to regenerated methods prior to said regeneration. In a third step, all non-regenerated methods are erased and the corresponding memory space placed at the disposal of the program.
This procedure does not only clean out unused methods, but also results in a reorganization between those methods that have been regenerated, so as to direct any references to the original methods immediately to appropriate regenerated methods instead of proceeding via an old method that is no longer used.
This is illustrated in the example of
In this example, analysis of the thread stacks shows that only the methods foo and bar are used and consequently foo and bar have not been referenced to the method apa.
All of the old methods, i.e. the methods foo 116, apa 118 and bar 120 shown in
When garbage collection of objects takes place, running the program normally stops while garbage collection takes place. Running of the program is restarted subsequent to the garbage collection and to the erasure of objects that are not in use.
Such a method can be used when applying the present invention.
However, the following method is preferable.
When practicing the inventive method, one thread is stopped at a time whilst the program is running, wherewith methods used for a stopped thread are selectively transferred to a list and the thread then restarted. The methods in the list are then regenerated and stored. All threads are later caused to be stopped at the same time, subsequent to having treated all threads this way, namely so that all used methods relating to the threads concerned have been regenerated. All methods that have not been regenerated are erased and all threads are restarted with the regenerated methods.
This method obviates the need to stop running the program, since the regeneration takes place intermittently.
As before mentioned, lock mechanisms are used in Java and corresponding languages. Different lock mechanisms can be selected. The important thing is typically to select the lock mechanism that is the most effective. For example, in some cases this may mean preventing more than one thread having access to a given object at the same time as another thread. In other cases, for example, if there is no contention on a lock, then a thin lock-based mechanism may be preferred over an inflated or fat-lock mechanism
A synchronization problem exists when several threads desire access to one and the same object or source. In order to solve this problem in Java, each thread endeavors to reach the source lock. The lock mechanism can be implemented in various ways. The effectiveness of different lock mechanisms will depend on how threads endeavor to obtain access to the locks and whether different threads try to access the same synchronized sources.
According to a preferred embodiment, when locking mechanisms are used the most effective locking mechanisms are identified in a step prior to said first step, and the methods that use a thus identified locking mechanism are regenerated.
With respect for garbage collecting algorithms, these also need to be selected. Many object oriented languages use garbage collection. This means that the programmer need not instruct the system explicitly that a certain object is no longer required. The system is responsible for this detection, and reclaims the part of the memory occupied by the object. A number of different algorithms have been proposed for effective implementation of this detection and reclaim. It has been found that different algorithms are best for different applications. The choice of the best garbage collecting algorithm for the program application being run is highly significant in achieving maximum execution rate in respect of the program concerned.
According to another preferred embodiment of the invention, when different garbage collecting algorithms are used the allocation and length of life of the various objects are determined in a step prior to said first method step, whereafter the most effective garbage collecting algorithm is caused to be identified and methods that are dependent on the requisite garbage collecting algorithms are regenerated and remaining garbage collecting algorithms then erased.
Application of the preferred embodiments provides a highly effective method for optimizing methods, thread management, and memory management, where a generic feature resides in the identification and regeneration of methods so as to not load the system with unused methods.
In some instances the invention can be used to help determine the best locking mechanism to be used with a particular method. In accordance with one embodiment of the invention, the JVM or run-time environment may employ various locking mechanisms by which the resource that provides a requested method is locked for use by the application program. For example, in many cases the program will be able to achieve a faster lock on a particular method using an uncontended lock mechanism (sometimes referred to as a “thin lock”). However, in other cases the program may be able to achieve a faster lock on another method using a contended lock mechanism (for example an “inflated” or “fat” lock). Since the invention allows regeneration of a method that uses a different locking mechanism, it can keep those methods or those versions of the methods that use the best locking mechanism, and delete the others. In this way the method may be modified by the JVM so that, for example, when a request is received to access a particular source lock, the system guesses that this particular source lock request requires, e.g. a fat lock. The system then attempts to try a fat lock and access the method. Following a successful attempt, the program returns to process the next request; otherwise the thread waits on the source lock to be released.
Garbage Collection Mechanisms
In accordance with the invention, the process of garbage collection of unused methods is actually a two-fold process, requiring a first phase of adaptive optimization, and a second phase of garbage collection of unused methods. While described below are various garbage collection methods that can be used with the invention, it will evident to one skilled in the art that additional types of garbage collection methods can be used within the spirit and scope of the invention.
The actual process of moving the methods to a single portion of the memory space and freeing up the rest of the memory space is commonly referred to as garbage collection.
Application Server Implementation
The foregoing description of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence.
|Citada||Data de depósito||Data de publicação||Requerente||Título|
|US5088036||17 jan. 1989||11 fev. 1992||Digital Equipment Corporation||Real time, concurrent garbage collection system and method|
|US5355483||18 jul. 1991||11 out. 1994||Next Computers||Asynchronous garbage collection|
|US5652883||23 maio 1995||29 jul. 1997||Microsoft Corporation||Computer method and system for conservative-stack and generational heap garbage collection|
|US5745705 *||13 dez. 1995||28 abr. 1998||Matsushita Electric Industrial Co., Ltd.||POS system|
|US5915255||23 abr. 1997||22 jun. 1999||Sun Microsystems, Inc.||Method and apparatus for referencing nodes using links|
|US5946487 *||10 jun. 1996||31 ago. 1999||Lsi Logic Corporation||Object-oriented multi-media architecture|
|US6041179||3 out. 1996||21 mar. 2000||International Business Machines Corporation||Object oriented dispatch optimization|
|US6463581||14 dez. 1998||8 out. 2002||International Business Machines Corporation||Method for determining reachable methods in object-oriented applications that use class libraries|
|US6560773 *||7 out. 1999||6 maio 2003||International Business Machines Corporation||Method and system for memory leak detection in an object-oriented environment during real-time trace processing|
|US6654951||14 dez. 1998||25 nov. 2003||International Business Machines Corporation||Removal of unreachable methods in object-oriented applications based on program interface analysis|
|US6658652 *||8 jun. 2000||2 dez. 2003||International Business Machines Corporation||Method and system for shadow heap memory leak detection and other heap analysis in an object-oriented environment during real-time trace processing|
|WO1999032978A1||17 dez. 1998||1 jul. 1999||Microsoft Corporation||Incremental garbage collection|
|1||Amitabh Srivastava, Unreachable Procedures in Object-Oriented Programming, 1992, ACM, pp. 1-10.|
|2||Pascal Fradet, Collecting More Garbage, 1994, ACM, pp. 1-10.|
|Citação||Data de depósito||Data de publicação||Requerente||Título|
|US7117214 *||16 fev. 2005||3 out. 2006||Bea Systems, Inc.||Systems and methods for maintaining transactional persistence|
|US7310650 *||9 fev. 2005||18 dez. 2007||Novell, Inc.||System, method and computer program product for migrating data from one database to another database|
|US7500229 *||25 jun. 2004||3 mar. 2009||Panasonic Corporation||Program converting method and storage medium|
|US7617226 *||10 fev. 2006||10 nov. 2009||Google Inc.||Document treadmilling system and method for updating documents in a document repository and recovering storage space from invalidated documents|
|US7634517 *||10 fev. 2006||15 dez. 2009||Google Inc.||System and method for dynamically updating a document repository without interrupting concurrent querying|
|US7769792 *||10 fev. 2006||3 ago. 2010||Google Inc.||Low overhead thread synchronization system and method for garbage collecting stale data in a document repository without interrupting concurrent querying|
|US20040268323 *||25 jun. 2004||30 dez. 2004||Matsushita Electric Industrial Co., Ltd||Program converting method, program and storage medium|
|US20050144170 *||16 fev. 2005||30 jun. 2005||Bea Systems, Inc.||Systems and methods for maintaining transactional persistence|
|Classificação nos Estados Unidos||1/1, 711/E12.009, 707/999.206|
|Classificação cooperativa||Y10S707/99957, G06F12/0253|
|12 ago. 2003||AS||Assignment|
Owner name: BEA SYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEA SYSTEMS STOCKHOLM ENGINEERING AB;REEL/FRAME:013869/0520
Effective date: 20030811
Owner name: BEA SYSTEMS STOCKHOLM ENGINEERING AB, SWEDEN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DAHLSTEDT, JOAKIM;REEL/FRAME:013869/0517
Effective date: 20030811
|8 jun. 2009||REMI||Maintenance fee reminder mailed|
|7 jul. 2009||FPAY||Fee payment|
Year of fee payment: 4
|7 jul. 2009||SULP||Surcharge for late payment|
|1 out. 2010||AS||Assignment|
Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEA SYSTEMS, INC.;REEL/FRAME:025084/0470
Effective date: 20100929
|8 mar. 2013||FPAY||Fee payment|
Year of fee payment: 8
|18 maio 2017||FPAY||Fee payment|
Year of fee payment: 12