1. Statement of the Technical Field
The present invention relates to the field of platform independent computing and more particularly to the management of platform independence for distributable objects in a platform independent computing application.
2. Description of the Related Art
Platform independent computing represents a modern advancement in computer science. The dawn of personal computing initially permitted only platform specific computing in which computer programs could be developed utilizing a particular computer programming language. To transform the generic source code of a computer program to object code required the use of a platform specific compiler and, for more complex programs, a platform specific linker. In particular, the platform specific compiler could be configured to translate the high level source code of the programming language to the specific machine instructions of a particular platform.
Several advantages are known to be associated with traditional, platform specific software development. Most notably, modern, platform specific compilers are known to be tightly coupled to hardware architecture of the underlying computing platform. Consequently, tremendous computing efficiencies can be recognized as the source code for a computer program can be tailored into very specific and highly efficient machine code for a target platform. Yet, platform specific software cannot be easily distributed across computing networks because in many circumstances, the ultimate host platform can differ from the target platform of the compiler which produced the platform specific code.
To address the desire to distribute computer programs to multiple, different host platforms without requiring the distribution of different versions of the same computing object, computer scientists developed platform independent computing technologies such as the Java, Erlang, Dylan and C# computing languages and associated development tools. Platform independent computing technologies allow software developers to develop a single set of source code for all target computing platforms. Compilers for platform independent computing languages typically produce intermediate byte code which can be interpreted at runtime in the target platform utilizing a virtual machine for a platform specific runtime environment.
A virtual machine within a runtime environment generally operates by loading required program objects when required through the operation of a class loader. In particular, class loaders provide the translation technology which can convert serialized byte code into named classes for execution in the virtual machine. Notably, class loaders can perform this conversion regardless of the storage means and location of the byte code. As a result, the virtual machine need not know the operational specifics associated with the file systems storing the byte code.
To address the desire to distribute computer programs to multiple, different host platforms without requiring the distribution of different versions of the same computing object, computer scientists developed platform independent computing technologies such as the JAVA™, ERLANG™, DYLAN™ and C#™ computing languages and associated development tools. Platform independent computing technologies allow software developers to develop a single set of source code for all target computing platforms. Compilers for platform independent computing languages typically produce intermediate byte code which can be interpreted at runtime in the target platform utilizing a virtual machine for a platform specific runtime environment.
Many assume that the performance problem of the platform independent paradigm has become insurmountable and have accepted the associated performance deficiencies. Yet others refuse to accept these deficiencies and, to address the operational deficiencies of such an environment, many developers resort to coding platform specific code for performance critical sections of a computer program. Yet, to do so can break the platform independence of the computer program.
The present invention addresses the deficiencies of the art in respect to platform independent computer programming and provides a novel and non-obvious method, system and apparatus for preserving platform independence with native accelerators for performance critical program objects. In this regard, a runtime environment which has been configured to preserve platform independence of a program while supporting native accelerators for performance critical program objects can include a virtual machine. The environment further can include a data store of platform independent program object implementations and a data store of platform specific program object implementations. Finally, the environment can include a class loader coupled to the virtual machine.
Importantly, the class loader can be programmed to selectively load platform specific program object implementations for performance critical program objects from the data store of platform specific program object implementations. Specifically, the class loader can load the platform specific program objects where such objects exist in addition to a platform independent implementation of the same program object. Otherwise the class loader can load platform independent program object implementations from the data store of platform independent program object implementations.
In a method for preserving platform independence of a program while supporting native accelerators for performance critical program objects, the method can include identifying a reference to a program object in a platform independent computer program and determining if a platform specific implementation of the program object has been separately stored in addition to a platform independent implementation of the program object. If it can be determined that a platform specific implementation of the program object has been separately stored in addition to a platform independent implementation of the program object, the platform specific implementation of the program object can be loaded in lieu of the platform independent implementation.
Notably, aside from the clear performance benefits of the present invention, the present invention also can provide significant development time and cost savings benefits. Specifically, through the use of the present invention, a software vendor can create a platform independent implementation of a program object and, only when required, need the vender provide a native implementation in order to enhance performance on key platforms. Thus, these native implementations can become a “drop in” and can be used only if found. Another advantage of this “drop in” native implementation approach is that it can be easy for a software vendor to pass the burden of the development of native implementations of performance critical program objects to other venders.
Additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The aspects of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
The accompanying drawings, which are incorporated in and constitute part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. The embodiments illustrated herein are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown, wherein:
The present invention is a method, system and apparatus for preserving platform independence with native accelerators for performance critical program objects. In accordance with the present invention, a virtual machine can be configured with a custom class loader programmed to selectively load program objects based upon whether the named program object is deemed performance critical. For a program object deemed to be performance critical in nature, the class loader first can attempt to load a platform specific, “native” implementation of the program object. If a platform specific implementation of the program object cannot be located or loaded, a platform independent, “generic” implementation of the program object can be loaded instead.
In this way, the platform independence of the computer program can be preserved, while platform specific implementation of critical program objects can be utilized to avoid the performance deficiencies of the conventional virtual machine. In this regard, a purely platform independent architecture always can be presumed excepting for when a performance critical object is to be loaded. Even then, however, a platform independent program object can be loaded unless a native accelerated implementation can be located. Consequently, at any time a native accelerated implementation for a performance critical program object can be provided without breaking the platform independent nature of the computer program.
In further illustration,
In more particular illustration,
Whenever an object reference is identified in decision block 230, in block 250 a data store of native, accelerated, platform specific object implementations can searched to determine if a native, accelerated, platform specific implementation for the referenced object can be located. If in decision block 260 a native, accelerated, platform specific implementation for the referenced object can be located, in block 270 the located program object can be loaded. Otherwise, in block 280, a default, platform independent implementation of the referenced program object can be loaded.
In more particular illustration,
In an alternative and preferred aspect of the invention, a class loader which differs from a standard class loader need not be provided. Rather, in the alternative aspect of the invention, both a native implementation and a default implementation of a program object can be provided and logic within the default program object can be provided to specify to the default class loader which implementation to utilize at realtime. In this way, providing a custom class loader to include the foregoing logic as described in
The present invention can be realized in hardware, software, or a combination of hardware and software. An implementation of the method and system of the present invention can be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system, or other apparatus adapted for carrying out the methods described herein, is suited to perform the functions described herein.
A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein. The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which, when loaded in a computer system is able to carry out these methods.
Computer program or application in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a) conversion to another language, code or notation; b) reproduction in a different material form. Significantly, this invention can be embodied in other specific forms without departing from the spirit or essential attributes thereof, and accordingly, reference should be had to the following claims, rather than to the foregoing specification, as indicating the scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
6282702 | Ungar | Aug 2001 | B1 |
6289506 | Kwong et al. | Sep 2001 | B1 |
6295643 | Brown et al. | Sep 2001 | B1 |
6330709 | Johnson et al. | Dec 2001 | B1 |
6342907 | Petty et al. | Jan 2002 | B1 |
6453460 | Keyes | Sep 2002 | B1 |
6530080 | Fresko et al. | Mar 2003 | B2 |
6634022 | Leermakers | Oct 2003 | B1 |
6654954 | Hicks | Nov 2003 | B1 |
6675230 | Lewallen | Jan 2004 | B1 |
6675375 | Czajkowski | Jan 2004 | B1 |
6925638 | Koved et al. | Aug 2005 | B1 |
7065743 | Blais et al. | Jun 2006 | B2 |
7162711 | Czajkowski et al. | Jan 2007 | B2 |
7185102 | Swaminathan et al. | Feb 2007 | B1 |
7200842 | Susser et al. | Apr 2007 | B1 |
7213240 | Wong et al. | May 2007 | B2 |
20030088860 | Wang | May 2003 | A1 |
20050063575 | Ma et al. | Mar 2005 | A1 |
20060080635 | Anwar et al. | Apr 2006 | A1 |
Number | Date | Country | |
---|---|---|---|
20060168567 A1 | Jul 2006 | US |