Contextual optimization for data storage systems

• US 10,437,790 B1
• Filed: 09/28/2016
• Issued: 10/08/2019
• Est. Priority Date: 09/28/2016
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Paterra, Frank Charles, Neilsen, Eric
• Primary Examiner(s): Vo, Truong V
• Application Number:
  US15/279,296
• Time in Patent Office: 1,105 Days
• Field of Search: 707704
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/122 using management policies backup systems G06F11/1446; file migration policies for HSM systems G06F16/185
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/1827 Management specifically adapted to NAS management of storage area networks [SAN] G06F3/067
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/566 Grouping or aggregating service requests, e.g. for unified processing

Abstract

A data storage system implements aggregation, bifurcation, and/or reduction techniques to improve the efficiency of processing data storage requests. Data storage requests and/or their associated payloads may be aggregated based on one or more parameters. Data to be the stored and the associated commands may be separated so as to optimize a system'"'"'s throughput and latency for each. Furthermore, extraneous commands and requests may be reduced or eliminated based on heuristics associated with the requests and the data.

Claims

1. A computer-implemented method, comprising:

receiving, from a client entity, a programmatic request to store data on a data storage of a server entity, the data storage comprising a file system, the programmatic request comprising predetermined responses to one or more component requests from the data storage;

determining whether the data to be stored has a size lower than a designated threshold;

as a result of determining that the data has a size lower than the designated threshold, and based at least in part on the predetermined responses, executing an associated write command by at least omitting one or more additional file system commands prescribed by the file system in connection with the write command; and

returning an outcome of the programmatic request to the client entity.

2. The computer-implemented method of claim 1, wherein the programmatic request includes the data to be stored on the data storage.

3. The computer-implemented method of claim 1, wherein the outcome is an exception resulting at least in part from the programmatic request being incorrect.

4. The computer-implemented method of claim 1, wherein the omitting one or more additional file system commands is based at least in part on one or more characteristics of the file system of the data storage and one or more parameters of the programmatic request to store data.

5. A system, comprising:

at least one processor; and

at least one memory comprising instructions that, in response to execution by the at least one processor, cause the system to implement one or more services, wherein the one or more services;

receive, from a client entity, a programmatic request to store data on a data storage of a server entity, the data storage comprising a file system, the programmatic request includes predetermined responses to incidental component requests from the data storage; and

process the programmatic request by at least;

executing an associated write command by at least attempting to store the data on the data storage while omitting one or more additional file system commands associated with the write command based at least in part on the predetermined responses; and

returning an outcome of the programmatic request to the client entity.

6. The system of claim 5, wherein the programmatic request is an API call.

7. The system of claim 5, wherein the one or more services further omit the one or more additional file system commands in connection with executing the associated write command as a result of a policy.

8. The system of claim 7, wherein the policy is associated with the one or more services.

9. The system of claim 7, wherein the policy is associated with a customer associated with the client entity.

10. The system of claim 7, wherein the policy defines a data threshold size for the data, below which the one or more services omit the one or more additional file system commands.

11. The system of claim 5, wherein the programmatic request includes the data associated with the additional file system commands.

12. The system of claim 5, wherein the outcome is an exception.

13. A non-transitory computer-readable storage medium comprising executable instructions that, as a result of being executed by one or more processors of a computer system, cause the computer system to at least:

receive, from a client entity, a programmatic request to store data on a data storage of a server entity, the data storage configured with a file system; and

process the programmatic request by at least;

determining a set of write commands based at least in part on the programmatic request;

executing a write command of the set of write commands by at least attempting to store the data on the data storage while omitting one or more other file system commands of the set of write commands by at least providing predetermined responses to one or more component requests from the data storage, the predetermined responses obtained from the programmatic request; and

returning an outcome of the programmatic request to the client entity.

14. The non-transitory computer-readable storage medium of claim 13, wherein the programmatic request includes one or more programmatic subrequests related to the programmatic request.

15. The non-transitory computer-readable storage medium of claim 13, wherein the other file system commands are associated with a previously existing version of the data to be stored.

16. The non-transitory computer-readable storage medium of claim 13, wherein the programmatic request is associated with a new directory in the file system.

17. The non-transitory computer-readable storage medium of claim 13, wherein processing the programmatic request includes determining whether to omit the other file system commands in connection with executing the write command.

18. The non-transitory computer-readable storage medium of claim 13, wherein an outcome of the programmatic request is provided to a requestor via an entity through which the programmatic request is received.

19. The non-transitory computer-readable storage medium of claim 13, wherein an exception resulting from processing the programmatic request is provided to a requestor via an entity through which the programmatic request is received.

20. The non-transitory computer-readable storage medium of claim 13, wherein the programmatic request is a web service call.