Dynamic service resource control
US-9223623-B2 · Dec 29, 2015 · US
US9262415B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9262415-B2 |
| Application number | US-201314075577-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 8, 2013 |
| Priority date | Nov 8, 2013 |
| Publication date | Feb 16, 2016 |
| Grant date | Feb 16, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed herein are system, method, and computer program product embodiments for storing and accessing data in a shared disk database system using a timestamp range to improve cache efficiency. An embodiment operates by retrieving, by a node, from a shared storage. a blockmap identity and a root page associated with a data request, based on a determination that the blockmap identity associated with a data request is present in a cache. The embodiment continues, retrieving, by the node, the logical page by copying a stored logical page from the shared storage and setting a lower timestamp value of the logical page to a timestamp associated with the stored logical page and an upper timestamp value of the logical page to a timestamp associated with the data request, based on a determination that the logical page is not present in the cache.
Opening claim text (preview).
What is claimed is: 1. A method comprising: determining, in response to a data request associated with a timestamp, that a logical page associated with the data request and the timestamp is not present in a cache by determining that a blockmap identity associated with the time stamp is not present in the cache; retrieving, by a node, from a shared storage, the blockmap identity and a root page associated with the data request; retrieving, by the node, the logical page associated with the data request by copying a stored logical page from the shared storage to the cache; and indicating a range of valid timestamp values for the logical page with a lower timestamp value and an upper timestamp value, the indicating comprising setting the lower timestamp value of the logical page to a timestamp associated with the stored logical page, and setting the upper timestamp value of the logical page to the timestamp associated with the data request. 2. The method of claim 1 , wherein the timestamp associated with the stored logical page and the timestamp associated with the data request are monotonically increasing timestamps. 3. The method of claim 1 , wherein the timestamp associated with the stored logical page and the timestamp associated with the data request are 4 byte unsigned integers. 4. The method of claim 1 , wherein the root page and the logical page comprise mappings of logical page numbers to physical block numbers. 5. The method of claim 1 , wherein the determining that the logical page associated with the data request and the timestamp is not present in the cache further comprises determining that there is not a cached logical page matching the logical page in the data request where the timestamp of the data request falls within a timestamp range of the cached logical page. 6. The method of claim 1 , wherein the determination that the logical page is not present in the cache further comprises the determination that the root page does not point to a cached logical page. 7. The method of claim 1 , further comprising setting, by the node, an upper timestamp value of a cached logical page to the timestamp associated with the data request based on a determination that the root page points to the cached logical page and the upper timestamp value of the cached logical page is less than the timestamp associated with the data request. 8. The method of claim 1 , further comprising: retrieving, by the node, a blockmap page associated with the data request by copying a stored blockmap page from the shared storage to the cache and setting a lower timestamp value of the blockmap page to a timestamp associated with the stored blockmap page and an upper timestamp value of the blockmap page to the timestamp associated with the data request, based on a determination that the blockmap page is not present in the cache. 9. A system comprising: a shared disk database; and at least one node coupled to the shared disk database and configured to: determining, in response to a data request associated with a timestamp, that a logical page associated with the data request and the timestamp is not present in a cache by determining that a blockmap identity associated with the time stamp is not present in the cache; retrieve, from a shared storage, the blockmap identity and a root page associated with the data request; and retrieve the logical page associated with the data request by copying a stored logical page from the shared storage to the cache; and indicate a range of valid timestamp values for the logical page with a lower timestamp value and an upper timestamp value, the indicating comprising setting the lower timestamp value of the logical page to a timestamp associated with the stored logical page, and setting the upper timestamp value of the logical page to the timestamp associated with the data request. 10. The system of claim 9 , wherein the timestamp associated with the stored logical page and the timestamp associated with the data request are monotonically increasing timestamps. 11. The system of claim 9 , wherein the timestamp associated with the stored logical page and the timestamp associated with the data request are 4 byte unsigned integers. 12. The system of claim 9 , wherein the root page and the logical page comprise mappings of logical page numbers to physical block numbers. 13. The system of claim 9 , wherein the determination that the logical page associated with the data request and the time stamp is not present in the cache further comprises the determination that there is not a cached logical page matching the logical page in the data request where the timestamp of the data request falls within a timestamp range of the cached logical page. 14. The system of claim 9 , wherein the determination that the logical page is not present in the cache further comprises the determination that the root page does not point to a cached logical page. 15. The system of claim 9 , wherein the node is further configured to set an upper timestamp value of a cached logical page to the timestamp associated with the data request based on a determination that the root page points to the cached logical page and the upper timestamp value of the cached logical page is less than the timestamp associated with the data request. 16. The system of claim 9 , the node if further configured to: retrieve a blockmap page associated with the data request by copying a stored blockmap page from the shared storage to the cache set a lower timestamp value of the blockmap page to a timestamp associated with the stored blockmap page and an upper timestamp value of the blockmap page to the timestamp associated with the data request, based on a determination that the blockmap page is not present in the cache. 17. A non-transitory computer-readable device having instructions stored thereon, execution of which, by at least one node, causes the one node to perform operations comprising: determining, in response to a data request associated with a timestamp, that a logical page associated with the data request and the timestamp is not present in a cache by determining that a blockmap identity associated with the time stamp is not present in the cache; retrieving, by a node, from a shared storage, the blockmap identity and a root page associated with the data request; retrieving, by the node, the logical page associated with the data request by copying a stored logical page from the shared storage to the cache; and indicating a range of valid timestamp values for the logical page with a lower timestamp value and an upper timestamp value, the indicating comprising setting the lower timestamp value of the logical page to a timestamp associated with the stored logical page, and setting the upper timestamp value of the logical page to the timestamp associated with the data request. 18. The computer-readable device of claim 17 , wherein the timestamp associated with the stored logical page and the timestamp associated with the data request are monotonically increasing timestamps. 19. The computer-readable device of claim 17 , wherein the timestamp associated with the stored logical page and the timestamp associated with the data request are 4 byte unsigned integers. 20. The computer-readable device of claim 17 , wherein the instructions causes the one node to perform operations further comprising: retrieving a blockmap page associated with the data request by copying a stored blockmap page from the shared storage to the cache and setting a lower timestamp value
Plural cache memories · CPC title
for peripheral storage systems, e.g. disk cache · CPC title
Physics · mapped topic
Cache consistency protocols · CPC title
Database tuning (G06F16/2282 takes precedence; database performance monitoring G06F11/3409) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.