I/O amplification for determining to increase workload

Patent metadata

Field	Value
Publication number	US-10241688-B2
Application number	US-201715454151-A
Country	US
Kind code	B2
Filing date	Mar 9, 2017
Priority date	Mar 9, 2017
Publication date	Mar 26, 2019
Grant date	Mar 26, 2019

Abstract

An amplification number may be input into a storage subsystem interface. A processor in a storage system may receive an original input/output (I/O) request from an application. The processor may determine, in response to the amplification number being input, to duplicate the original I/O request one or more times. The processor may generate one or more duplicate I/O requests of the original I/O request. The processor may store the original I/O request in a general address space in the storage subsystem. The processor may store the one or more duplicate I/O requests in a reserved address space in the storage subsystem. The processor may execute the original I/O request and the one or more duplicate requests.

First claim

What is claimed is:

1. A computer-implemented method comprising:
inputting an amplification number into a storage subsystem interface;
receiving, by a processor in a storage subsystem, an original input/output (I/O) request from an application, wherein the application is a webpage;
determining, in response to the amplification number being input, to duplicate the original I/O request one or more times;
generating one or more duplicate I/O requests of the original I/O request for simultaneous execution with the original I/O request, wherein the amount of the one or more duplicate I/O requests corresponds to the amplification number;
storing the original I/O request in a general address space in the storage subsystem;
storing the one or more duplicate I/O requests in a reserved address space in the storage subsystem;
executing, simultaneously, the original I/O request in the general address space and all of the one or more duplicate I/O requests in the reserved address space;
determining that the original I/O request type is a write operation wherein the write operation alters the behavior of the storage subsystem;
duplicating the write operation of the original I/O request to the one or more duplicate I/O requests;
altering the behavior of the reserved address space of the storage subsystem by executing the write operation, wherein altering the behavior of the reserved address space includes changing a display feature of the webpage; and
merging the general address space and the reserved address space together, wherein the general address space and the reserved address space are automatically merged, upon meeting a performance metric threshold, by removing a virtual partition separating the general address space and the reserved address space.

2. The method of claim 1 , wherein generating the one or more duplicate I/O requests comprises:
identifying a block-size of the original I/O request; and
duplicating the block-size of the original I/O request identically to each of the one or more duplicate I/O requests.

3. The method of claim 2 , further comprising:
identifying a storage address of the original I/O request, wherein the storage address directs the original I/O request to be stored in the general address space of the storage subsystem;
generating a tag, wherein the tag is a fixed offset value;
adding the tag to the storage address of the original I/O request, wherein adding the tag to the storage address of the original I/O request creates a new storage address; and
storing the one or more duplicate I/O requests in the new storage address, wherein the new storage address directs the one or more duplicate I/O requests to be stored in the reserved address space of the storage subsystem.

4. The method of claim 1 , further comprising:
hiding the altered behavior of the reserved address space of the storage subsystem from the user, wherein hiding the altered behavior of the reserved address space includes not displaying the changed display feature of the webpage to the user and displaying a loading delay of the webpage to the user, wherein the changed display feature of the webpage is an alteration to the appearance of the webpage, and wherein the loading delay is in response to the alteration to the appearance of the webpage;
providing the user with an observational performance impact report, wherein the observational performance impact report includes the effect of the one or more duplicate I/O requests on the storage subsystem after execution of the one or more duplicate I/O requests; and
determining, from the observational performance impact report, a maximum workload for the webpage.

5. The method of claim 4 , wherein the effect of the one or more duplicate I/O requests includes the effects of the one or more duplicate I/O requests on one or more computer components, wherein the one or more computer components include a memory, a file system, and a network.

6. The method of claim 4 , wherein the general address space and the reserved address space are automatically combined to increase the maximum workload for the webpage.

7. A system comprising:
a memory; and
a processor in communication with the memory, the processor being configured to perform operations comprising:
inputting an amplification number into a storage subsystem interface;
receiving an original input/output (I/O) request from an application, wherein the application is a webpage;
determining, in response to the amplification number being input, to duplicate the original I/O request one or more times;
generating one or more duplicate I/O requests of the original I/O request for simultaneous execution with the original I/O request, wherein the amount of the one or more duplicate I/O requests corresponds to the amplification number;
storing the original I/O request in a general address space in a storage subsystem;
storing the one or more duplicate I/O requests in a reserved address space in the storage subsystem;
executing, simultaneously, the original I/O request in the general address space and all of the one or more duplicate I/O requests in the reserved address space;
determining that the original I/O request type is a write operation wherein the write operation alters the behavior of the storage subsystem;
duplicating the write operation of the original I/O request to the one or more duplicate I/O requests;
altering the behavior of the reserved address space of the storage subsystem by executing the write operation, wherein altering the behavior of the reserved address space includes changing a display feature of the webpage; and
merging the general address space and the reserved address space together, wherein the general address space and the reserved address space are automatically merged, upon meeting a performance metric threshold, by removing a virtual partition separating the general address space and the reserved address space.

8. The system of claim 7 , wherein generating the one or more duplicate I/O requests comprises:
identifying a block-size of the original I/O request; and
duplicating the block-size of the original I/O request identically to each of the one or more duplicate I/O requests.

9. The system of claim 8 , further comprising:
identifying a storage address of the original I/O request, wherein the storage address directs the original I/O request to be stored in the general address space of the storage subsystem;
generating a tag, wherein the tag is a fixed offset value;
adding the tag to the storage address of the original I/O request, wherein adding the tag to the storage address of the original I/O request creates a new storage address; and
storing the one or more duplicate I/O requests in the new storage address, wherein the new storage address directs the one or more duplicate I/O requests to be stored in the reserved address space of the storage subsystem.

10. The system of claim 7 further comprising:
hiding the altered behavior of the reserved address space of the storage subsystem from the user, wherein hiding the altered behavior of the reserved address space includes not displaying the changed display feature of the webpage to the user and displaying a loading delay of the application to the user, wherein the changed display feature of the webpage is an alteration to the appearance of the webpage, and wherein the loading delay is in response to the alteration to the appearance of the webpage;
providing the user with an observational performance impact report, wherein the observational performance impact report includes the effect of the one or more duplicate I/O requests on the storage subsystem after execution of the one or more duplicate I/O requests; and
det

Assignees

• IBM

Inventors

• Ingram Samuel K
• Reyes Sergio
• Twichell Brian C
• Zhang Yijie

Classifications

• G06F3/065

  Replication mechanisms · CPC title

• G06F3/0619

  in relation to data integrity, e.g. data losses, bit errors · CPC title

• G06F17/30899

  Physics · mapped topic

• G06F13/1642

  with request queuing · CPC title

• G06F3/0613 Primary

  in relation to throughput · CPC title