Methods for facilitating persistent storage of in-memory databases and devices thereof

• US 9,934,008 B2
• Filed: 06/18/2014
• Issued: 04/03/2018
• Est. Priority Date: 06/18/2014
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Santry, Douglas Joseph
• Primary Examiner(s): LOUIE, JUE WANG
• Application Number:
  US14/308,272
• Publication Number:
  US 20150370544A1
• Time in Patent Office: 1,385 Days
• Field of Search: None
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 9/44521 Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

A method, non-transitory computer readable medium, and application host computing device that parses assembly language code to identify a transaction block including an assignment to a memory location, the assembly language code associated with an application and output by a compiler. The assembly language code is modified to insert an invocation of a plurality of functions collectively configured to facilitate persistent storage of one or more data updates associated with the assignment at run-time. The assembly language code is assembled to generate object code and the object code is linked with at least a run-time library including a definition for each of the plurality of inserted functions to generate an executable file for the application.

Claims

1. A computing device, comprising:

a memory containing a machine readable medium comprising machine executable code having stored thereon instructions for facilitating persistent storage of in-memory databases; and

a hardware processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to;

identify a transaction block in assembly language code associated with an application, the transaction block comprising an assignment to a location in an in-memory database;

modify the assembly language code to insert one or more functions configured to, when invoked at run-time;

determine when the location associated with the assignment in the transaction block of the assembly language code is within a range of a region mapped to the application by comparing the location against the range of the region mapped to the application; and

facilitate persistent storage of one or more data updates associated with the assignment in the transaction block of the assembly language code by inserting the location and a size associated with the assignment in the transaction block of the assembly language code into an entry of a data structure and replicating data associated with the entry to persistent data storage, only when the location is within the range of the region mapped to the application; and

assemble the assembly language code to generate object code and link the object code with a run-time library comprising a definition for the inserted functions to generate an executable file.

2. The device of claim 1, wherein the functions comprise a first function an invocation of which is inserted following a begin instruction of the transaction block, a second function an invocation of which is inserted proximate to the assignment, and a third function an invocation of which is inserted following an end instruction of the transaction block and outside of the transaction block.

3. The device of claim 2, wherein the begin instruction is an xbegin instruction, the assignment is associated with a mov instruction, and the end instructions is an xend instruction.

4. The device of claim 1, wherein the data structure comprises a transaction descriptor and the functions comprise a first function that allocates the transaction descriptor and places a pointer to the transaction descriptor on a stack, a second function that inserts at least the location and the size associated with the assignment into the entry of the transaction descriptor, and a third function that replicates data associated with the entry of the transaction descriptor to persistent data storage.

5. The device of claim 4, wherein the location in the in-memory database is a location in a dynamic random access memory (DRAM), the persistent data storage comprises block-based disk storage, and the functions are further configured to facilitate persistent storage of the one or more data updates with byte-level granularity.

6. The device of claim 1, wherein the hardware processor coupled to the memory is further configured to execute the machine executable code to cause the hardware processor to execute the executable file and send the one or more data updates to persistent data storage by invoking the functions at run-time.

7. The device of claim 1, wherein the location comprises a memory address associated with the assignment in the transaction block and the size is based on a type of the assignment.

8. A method of facilitating persistent storage of in-memory databases, comprising:

identifying, by a computing device, a transaction block in assembly language code associated with an application, the transaction block comprising an assignment to a location in an in-memory database;

modifying, by the computing device, the assembly language code to insert one or more functions configured to, when invoked at run-time;

determine when the location associated with the assignment in the transaction block of the assembly language code is within a range of a region mapped to the application by comparing the location against the range of the region mapped to the application; and

facilitate persistent storage of one or more data updates associated with the assignment in the transaction block of the assembly language code by inserting the location and a size associated with the assignment in the transaction block of the assembly language code into an entry of a data structure and replicating data associated with the entry to persistent data storage, only when the location is within the range of the region mapped to the application; and

assembling, by the computing device, the assembly language code to generate object code and linking the object code with a run-time library comprising a definition for the inserted functions to generate an executable file.

9. The method of claim 8, wherein the functions comprise a first function an invocation of which is inserted following a begin instruction of the transaction block, a second function an invocation of which is inserted proximate to the assignment, and a third function an invocation of which is inserted following an end instruction of the transaction block and outside of the transaction block.

10. The method of claim 9, wherein the begin instruction is an xbegin instruction, the assignment is associated with a mov instruction, and the end instructions is an xend instruction.

11. The method of claim 8, wherein the data structure comprises a transaction descriptor and the functions comprise a first function that allocates the transaction descriptor and places a pointer to the transaction descriptor on a stack, a second function that inserts at least the location and the size associated with the assignment into the entry of the transaction descriptor, and a third function that replicates data associated with the entry of the transaction descriptor to persistent data storage.

12. The method of claim 11, wherein the location in the in-memory database is a location in a dynamic random access memory (DRAM), the persistent data storage comprises block-based disk storage, and the functions are further configured to facilitate persistent storage of the one or more data updates with byte-level granularity.

13. The method of claim 8, further comprising executing, by the computing device, the executable file and sending the one or more data updates to persistent data storage by invoking the functions at run-time.

14. The method of claim 8, wherein the location comprises a memory address associated with the assignment in the transaction block and the size is based on a type of the assignment.

15. A non-transitory machine readable medium having stored thereon instructions for facilitating persistent storage of in-memory databases comprising machine executable code which when executed by at least one machine, causes the machine to:

identify a transaction block in assembly language code associated with an application, the transaction block comprising an assignment to a location in an in-memory database;

modify the assembly language code to insert one or more functions configured to, when invoked at run-time;

determine when the location associated with the assignment in the transaction block of the assembly language code is within a range of a region mapped to the application by comparing the location against the range of the region mapped to the application; and

facilitate persistent storage of one or more data updates associated with the assignment in the transaction block of the assembly language code by inserting the location and a size associated with the assignment in the transaction block of the assembly language code into an entry of a data structure and replicating data associated with the entry to persistent data storage, only when the location is within the range of the region mapped to the application; and

assemble the assembly language code to generate object code and link the object code with a run-time library comprising a definition for the inserted functions to generate an executable file.

16. The medium of claim 15, wherein the functions comprise a first function an invocation of which is inserted following a begin instruction of the transaction block, a second function an invocation of which is inserted proximate to the assignment, and a third function an invocation of which is inserted following an end instruction of the transaction block and outside of the transaction block.

17. The medium of claim 16, wherein the begin instruction is an xbegin instruction, the assignment is associated with a mov instruction, and the end instructions is an xend instruction.

18. The medium of claim 15, wherein the data structure comprises a transaction descriptor and the functions comprise a first function that allocates the transaction descriptor and places a pointer to the transaction descriptor on a stack, a second function that inserts at least the location and the size associated with the assignment into the entry of the transaction descriptor, and a third function that replicates data associated with the entry of the transaction descriptor to persistent data storage.

19. The medium of claim 18, wherein the location in the in-memory database is a location in a dynamic random access memory (DRAM), the persistent data storage comprises block-based disk storage, and the functions are further configured to facilitate persistent storage of the one or more data updates with byte-level granularity.

20. The medium of claim 15, wherein the machine executable code when executed by the machine, further causes the machine to execute the executable file and send the one or more data updates to persistent data storage by invoking the functions at run-time.

21. The medium of claim 15, wherein the location comprises a memory address associated with the assignment in the transaction block and the size is based on a type of the assignment.