System and method for configuring a storage devcie based on prediction of host source
US-2020242038-A1 · Jul 30, 2020 · US
US2022398245A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2022398245-A1 |
| Application number | US-202117345533-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jun 11, 2021 |
| Priority date | Jun 11, 2021 |
| Publication date | Dec 15, 2022 |
| Grant date | — |
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.
The present disclosure relates to time aware caching. One method includes receiving an API request for data from a database, wherein the request defines a time window associated with the data, creating a first and second query based on the request, wherein the first query corresponds to a first chunk of the time window, and wherein the second query corresponds to a second chunk of the time window, hashing a first statement associated with the first query to produce a first key and hashing a second statement associated with the second query to produce a second key, retrieving a first portion of the data corresponding to the first chunk of the time window from cache responsive to a determination that the first key is in the cache, and retrieving a second portion of the data corresponding to the second chunk of the time window from the database responsive to a determination that the second key is not in the cache.
Opening claim text (preview).
What is claimed is: 1 . A method, comprising: receiving an application programming interface (API) request for data from a database, wherein the request defines a time window associated with the data; creating a first query and a second query based on the request, wherein the first query corresponds to a first chunk of the time window, and wherein the second query corresponds to a second chunk of the time window; hashing a first statement associated with the first query to produce a first key and hashing a second statement associated with the second query to produce a second key; retrieving a first portion of the data corresponding to the first chunk of the time window from cache responsive to a determination that the first key is in the cache; and retrieving a second portion of the data corresponding to the second chunk of the time window from the database responsive to a determination that the second key is not in the cache. 2 . The method of claim 1 , wherein the method includes caching the second portion of the data subsequent to retrieving the second portion of the data from the database. 3 . The method of claim 2 , wherein the method includes: receiving a subsequent API request for data from the database, wherein the subsequent request defines the time window associated with the data; creating the first query and the second query based on the subsequent request, wherein the first query corresponds to the first chunk of the time window, and wherein the second query corresponds to the second chunk of the time window; hashing the first statement associated with the first query to produce the first key and hashing the second statement associated with the second query to produce the second key; retrieving the first portion of the data corresponding to the first chunk of the time window from cache responsive to a determination that the first key is in the cache; and retrieving the second portion of the data corresponding to the second chunk of the time window from the cache responsive to a determination that the second key is in the cache. 4 . The method of claim 2 , wherein the method includes: receiving a further API request for data from the database, wherein the further request defines a different time window associated with the data, and wherein the different time window includes the second chunk; creating the second query and a third query based on the further request, wherein the third query corresponds to a third chunk of the different time window; hashing the second statement associated with the second query to produce the second key and hashing a third statement associated with the third query to produce a third key; retrieving the second portion of the data corresponding to the second chunk from cache responsive to a determination that the second key is in the cache; and retrieving a third portion of the data corresponding to the third chunk of the different time window from the database responsive to a determination that the third key is not in the cache. 5 . The method of claim 1 , wherein the data is time series data. 6 . The method of claim 1 , wherein the method includes hashing the first statement and hashing the second statement using a SHA1 hash. 7 . The method of claim 1 , wherein the method includes dividing the time window into a plurality of chunks. 8 . The method of claim 7 , wherein the method includes determining a duration of each chunk based on a duration of the time window. 9 . A non-transitory machine-readable medium having instructions stored thereon which, when executed by a processor, cause the processor to: receive an application programming interface (API) request for data from a database, wherein the request defines a time window of the data; create a first query and a second query based on the request, wherein the first query corresponds to a first chunk of the time window, and wherein the second query corresponds to a second chunk of the time window; hash a first statement associated with the first query and a second statement associated with the second query; retrieve a first portion of the data corresponding to the first chunk of the time window from cache responsive to a determination that a key corresponding to the hash of the first statement is in the cache; and retrieve the first portion of the data corresponding to the first chunk of the time window from the database responsive to a determination that the key corresponding to the hash of the first statement is not in the cache. 10 . The medium of claim 9 , including instructions to: retrieve a second portion of the data corresponding to the second chunk of the time window from cache responsive to a determination that a key corresponding to the hash of the second statement is in the cache; and retrieve the second portion of the data corresponding to the second chunk of the time window from the database responsive to a determination that the second key is not in the cache. 11 . The medium of claim 9 , wherein the first chunk and the second chunk are a same duration. 12 . The medium of claim 9 , wherein the first chunk and the second chunk are each 10 minutes in duration. 13 . The medium of claim 9 , including instructions to retrieve the first portion of the data corresponding to the first chunk of the time window from the database responsive to an indication made by a user not to retrieve the first portion of the data from cache. 14 . The medium of claim 9 , including instructions to retrieve the first portion of the data corresponding to the first chunk of the time window from the database responsive to a determination that the first portion of the data does not exceed an age threshold. 15 . The medium of claim 9 , wherein the data describes a performance indicator for a cellular tower. 16 . The medium of claim 9 , wherein the data is sensor data. 17 . A system, comprising: a request engine configured to receive an application programming interface (API) request for data from a database, wherein the request defines a time window of the data; a query engine configured to create a first query and a second query based on the request, wherein the first query corresponds to a first chunk of the time window, and wherein the second query corresponds to a second chunk of the time window; a hash engine configured to hash a first statement associated with the first query and a second statement associated with the second query; a cache engine configured to retrieve a first portion of the data corresponding to the first chunk of the time window from cache responsive to a determination that a key corresponding to the hash of the first statement is in the cache; and a database engine configured to retrieve the first portion of the data corresponding to the first chunk of the time window from the database responsive to a determination that the key corresponding to the hash of the first statement is not in the cache. 18 . The system of claim 17 , wherein the first chunk and the second chunk have different durations. 19 . The system of claim 17 , wherein a duration of the first chunk is exceeded by a duration of the second chunk. 20 . The system of claim 19 , wherein the first chunk is associated with a beginning of the time window.
Query optimisation · CPC title
Buffers; Shared memory; Pipes · CPC title
Run-time optimisation · CPC title
Temporal data queries · CPC title
using cached or materialised query results · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.