Computer architecture and method of operation for multi-computer distributed processing with finalization of objects

• US 20060265705A1
• Filed: 10/25/2005
• Published: 11/23/2006
• Est. Priority Date: 04/21/2005
• Status: Active Grant

• Current Assignee: Waratek Limited (Waratek Holdings Ltd.)
• Original Assignee: Waratek Pty Limited
• Inventors: Holt, John Matthew
• Granted Patent: US 8,028,299 B2
• Time in Patent Office: Days
• US Class Current: 717/169
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 8/456 Parallelism detection

Abstract

The present invention discloses a modified computer architecture (50, 71, 72) which enables an applications program (50) to be run simultaneously on a plurality of computers (M1, . . . Mn). Shared memory at each computer is updated with amendments and/or overwrites so that all memory read requests are satisfied locally. During initial program loading (75), or similar, instructions which result in memory being re-written or manipulated are identified (92). Additional instructions are inserted (103) to cause the equivalent memory locations at all computers to be updated. In particular, the finalization of JAVA language classes and objects is disclosed (162, 163) so finalization only occurs when the last class or object present on all machines is no longer required.

Claims

1. A multiple computer system having at least one application program each written to operate only on a single computer but running simultaneously on a plurality of computers interconnected by a communications network, wherein different portions of said application program(s) execute substantially simultaneously on different ones of said computers and for each said portion a like plurality of substantially identical objects are created, each in the corresponding computer and each having a substantially identical name, and wherein all said identical objects are collectively deleted when each one of said plurality of computers no longer needs to refer to their corresponding object.

2. The system as claimed in claim 1 wherein each said computer includes a distributed run time means with the distributed run time means of each said computer able to communicate with all other computers whereby if a portion of said application program(s) running on one of said computers no longer needs to refer to an object in that computer then the identity of the unreferenced object is transmitted by the distributed run time means of said one computer to a shared table accessible by all the other computers.

3. The system as claimed in claim 2 wherein each said application program is modified before, during, or after loading by inserting a finalization routine to modify each instance at which said application program no longer needs to refer to an object.

4. The system as claimed in claim 3 wherein said inserted finalization routine modified a pre-existing finalization routine to enable the pre-existing finalization routine to execute if all computers no longer need to refer to their corresponding object, and to disable the pre-existing finalization routine if at least one computer does not to refer to a corresponding object.

5. The system as claimed in claim 4 wherein the application program is modified in accordance with a procedure selected from the group of procedures consisting of re-compilation at loading, pre-compilation prior to loading, compilation prior to loading, just-in-time compilation, and re-compilation after loading and before execution of the relevant portion of application program.

6. The system as claimed in claim 2 wherein said modified application program is transferred to all said computers in accordance with a procedure selected from the group consisting of master/slave transfer, branched transfer and cascaded transfer.

7. A plurality of computers interconnected via a communications link and operating simultaneously at least one application program each written to operate only on a single computer, wherein each said computer substantially simultaneously executes a different portion of said application program(s), each said computer in operating its application program portion needs, or no longer needs to refer to an object only in local memory physically located in each said computer, the contents of the local memory utilized by each said computer is fundamentally similar but not, at each instant, identical, and every one of said computers has a finalization routine which deletes a non-referenced object only if each one of said plurality of computers no longer needs to refer to their corresponding object.

8. The plurality of computers as claimed in claim 7 wherein the local memory capacity allocated to the or each said application program is substantially identical and the total memory capacity available to the or each said application program is said allocated memory capacity.

9. The plurality of computers as claimed in claim 7 wherein all said distribution update means communicate via said communications link at a data transfer rate which is substantially less than the local memory read rate.

10. The plurality of computers as claimed in claim 7 wherein at least some of said computers are manufactured by different manufacturers and/or have different operating systems.

11. A method of running simultaneously on a plurality of computers at least one application program each written to operate only on a single computer, said computers being interconnected by means of a communications network, said method comprising the steps of:

(i) executing different portions of said application program(s) on different ones of said computers and for each said portion creating a like plurality of substantially identical objects each in the corresponding computer and each having a substantially identical name, and

(ii) deleting all said identical objects collectively when all of said plurality of computers no longer need to refer to their corresponding object.

12. A method as claimed in claim 11 including the further step of:

(iii) providing each said computer with a distributed run time means to communicate between said computers via said communications network.

13. A method as claimed in claim 12 including the further step of:

(iv) providing a shared table accessible by each said distributed run time means and in which is stored the identity of any computer which no longer requires to access an object, together with the identity of the object.

14. A method as claimed in claim 13 including the further step of:

(v) associating a counter means with said shared table, said counter means storing a count of the number of said computers which no longer require to access said object.

15. A method as claimed in claim 14 including the further step of:

(vi) providing an additional computer on which said shared program does not run and which hosts said shared table and counter, said additional computer being connected to said communications network.

37. A computer program product comprising a set of program instructions stored in a storage medium and operable to permit a plurality of computers to carry out the method as claimed in claim 11.

39. A plurality of computers interconnected via a communication network and operable to ensure consistent initialization of an application program written to operate only on a single computer but running simultaneously on said computers, said computers being programmed to carry out the method as claimed in claim 11.

41. A plurality of computers interconnected via a communication network and operable to ensure consistent initialization of an application program written to operate only on a single computer but running simultaneously on said computers, said computers being loaded with the computer program product as claimed in claim 37.

16. A method of ensuring consistent finalization of an application program written to operate only on a single computer but different portions of which are to be executed substantially simultaneously each on a different one of a plurality of computers interconnected via a communications network, said method comprising the steps of:

(i) scrutinizing said application program at, or prior to, or after loading to detect each program step defining an finalization routine, and

(ii) modifying said finalization routine to ensure collective deletion of corresponding objects in all said computers only when each one of said computers no longer needs to refer to their corresponding object.

17. The method as claimed in claim 16 wherein said finalization routine is modified to execute to clean-up an object once only and on only one of said computers and when all of said computers no longer need to refer to said object.

18. The method claimed in claim 16 wherein step (ii) comprises the steps of:

(iii) loading and executing said finalization routine on one of said computers,

(iv) modifying said finalization routine by said one computer, and

(v) transferring said modified finalization routine to each of the remaining computers.

19. The method as claimed in claim 18 wherein said modified finalization routine is supplied by said one computer direct to each of said remaining computers.

20. The method as claimed in claim 18 wherein said modified finalization routine is supplied in cascade fashion from said one computer sequentially to each of said remaining computers.

21. The method claimed in claim 16 wherein step (ii) comprises the steps of:

(vi) loading and modifying said finalization routine on one of said computers,

(vii) said one computer sending said unmodified finalization routine to each of the remaining computers, and

(viii) each of said remaining computers modifying said finalization routine after receipt of same.

22. The method claimed in claim 21 wherein said unmodified finalization routine is supplied by said one computer directly to each of said remaining computers.

23. The method claimed in claim 21 wherein said unmodified finalization routine is supplied in cascade fashion from said one computer sequentially to each of said remaining computers.

24. The method as claimed in claim 16 including the further step of:

(ix) modifying said application program utilizing a procedure selected from the group of procedures consisting of re-compilation at loading, pre-compilation prior to loading, compilation prior to loading, just-in-time compilation, and re-compilation after loading and before execution of the relevant portion of application program.

25. The method as claimed in claim 16 including the further step of:

(x) transferring the modified application program to all said computers utilizing a procedure selected from the group consisting of master/slave transfer, branched transfer and cascaded transfer.

29. The method claimed in claim 17 wherein step (ii) comprises the steps of:

(iii) loading and executing said finalization routine on one of said computers,

(iv) modifying said finalization routine by said one computer, and

(v) transferring said modified finalization routine to each of the remaining computers.

30. The method as claimed in claim 29 wherein said modified finalization routine is supplied by said one computer direct to each of said remaining computers.

31. The method as claimed in claim 29 wherein said modified finalization routine is supplied in cascade fashion from said one computer sequentially to each of said remaining computers.

32. The method claimed in claim 17 wherein step (ii) comprises the steps of:

(vi) loading and modifying said finalization routine on one of said computers,

(vii) said one computer sending said unmodified finalization routine to each of the remaining computers, and

(viii) each of said remaining computers modifying said finalization routine after receipt of same.

33. The method claimed in claim 32 wherein said unmodified finalization routine is supplied by said one computer directly to each of said remaining computers.

34. The method claimed in claim 32 wherein said unmodified finalization routine is supplied in cascade fashion from said one computer sequentially to each of said remaining computers.

35. The method as claimed in claim 17 including the further step of:

(ix) modifying said application program utilizing a procedure selected from the group of procedures consisting of re-compilation at loading, pre-compilation prior to loading, compilation prior to loading, just-in-time compilation, and re-compilation after loading and before execution of the relevant portion of application program.

36. The method as claimed in claim 17 including the further step of:

(x) transferring the modified application program to all said computers utilizing a procedure selected from the group consisting of master/slave transfer, branched transfer and cascaded transfer.

38. A computer program product comprising a set of program instructions stored in a storage medium and operable to permit a plurality of computers to carry out the method as claimed in claim 16.

40. A plurality of computers interconnected via a communication network and operable to ensure consistent initialization of an application program written to operate only on a single computer but running simultaneously on said computers, said computers being programmed to carry out the method as claimed in claim 16.

42. A plurality of computers interconnected via a communication network and operable to ensure consistent initialization of an application program written to operate only on a single computer but running simultaneously on said computers, said computers being loaded with the computer program product as claimed in claim 38.

26. In a multiple thread processing computer operation in which individual threads of a single application program written to operate only on a single computer are simultaneously being processed each on a corresponding different one of a plurality of computers interconnected via a communications link, and in which objects in local memory physically associated with the computer processing each thread have corresponding objects in the local memory of each other said computer, the improvement comprising collectively deleting all said corresponding objects when each one of said plurality of computers no longer needs to refer to their corresponding object.

27. The improvement as claimed in claim 26 wherein an object residing in the memory associated with one said thread and to be deleted has its identity communicated by the computer of said one thread to a shared table accessible by all other said computers.

28. The improvement as claimed in claim 26 wherein an object residing in the memory associated with one said thread and to be deleted has its identity transmitted to the computer associated with another said thread and is transmitted thereby to a shared table accessible by all said other computers.