# US 2026/0010310 A1 · Data reduction management

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0010310 A1
- Document ID: US20260010310A1
- Status: Published application
- Kind: A1
- Application number: 18/762,721
- Filed: 2024-07-03
- Published: 2026-01-08
- Earliest claimed: 2024-07-03
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Owen Martin; Ramesh Doddaiah
- Web page: https://patentgrep.com/patent/US20260010310A1

## CPC

- G06F 3/0653: {Monitoring storage devices or systems}
- G06F 3/0608: {Saving storage space on storage systems}
- G06F 3/061: {Improving I/O performance}
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/067: {Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

One or more aspects of the present disclosure relate to managing data reduction in a storage system during burst workloads. In embodiments, input/output (IO) operations received by a storage array are monitored to identify a burst workload based on a predefined threshold of IO operations per second (IOPS). In addition, the compression of data corresponding to IO write operations in the burst workload is deferred during the identified burst workload by temporarily storing the data in an uncompressed format. Further, the data is compressed during a self-healing period after a delay period. For example, the delay period is after the identified burst workload.

## Claims

### Claim 1

A method comprising:
monitoring input/output (IO) operations received by a storage array to identify a burst workload based on a predefined threshold of IO operations per second (IOPS), wherein the monitoring includes tracking a number, type, size, and frequency of IO operations targeting each storage group of the storage array and maintaining a data structure of metrics corresponding to the monitored IO operations;
deferring compression of data corresponding to IO write operations in the burst workload during the identified burst workload by temporarily storing the data in an uncompressed format, wherein the deferring includes allocating a portion of persistent storage to temporarily destage the IO write requests and their corresponding data to disk during the burst workload; and
compressing the data during a data compression self-healing period after a delay period, wherein the delay period is after the identified burst workload, and wherein the data compression self-healing period is a period when the storage array has available resources to perform compression operations on the temporarily stored uncompressed data, and wherein the data compression self-healing period is specifically triggered by detecting that the storage array has transitioned from a high resource utilization state during the burst workload to a lower resource utilization state with sufficient processing capacity available for background compression operations.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
defining a duration of the delay period based on an availability of storage array resources.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
defining a start and duration of the self-healing period based on available idle resource utilization of the storage array, wherein the available idle resource utilization represents unused processing capacity of the storage array.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining a compressibility of the data corresponding to each IO write operation in the burst workload; and
applying adaptive compression algorithms to the data based on the determined compressibility of the data.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
selecting between light compression and heavy compression based on a current load of the storage array and the compressibility of the data, wherein the storage array's current load refers to the level of resource utilization of the storage array at a given time.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
identifying the burst workload by calculating a Burst Heat Index (BHI) for each storage group in the storage array based on a score biased towards IO write operations.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
identifying each storage group targeted by IO operations in the burst workload using the BHI.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
identifying an IO signature of the IO operations received by the storage array.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
determining whether the IO signature of the IO operations matches an IO shapelet defining a burst workload type.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
defining a burst workload type based on a threshold of IOPS received by the storage array during a time window threshold.

### Claim 11

An apparatus with a memory and processor, the apparatus configured to:
monitor input/output (IO) operations received by a storage array to identify a burst workload based on a predefined threshold of IO operations per second (IOPS), wherein the monitoring includes tracking a number, type, size, and frequency of IO operations targeting each storage group of the storage array and maintaining a data structure of metrics corresponding to the monitored IO operations;
defer compression of data corresponding to IO write operations in the burst workload during the identified burst workload by temporarily storing the data in an uncompressed format, wherein the deferring includes allocating a portion of persistent storage to temporarily destage the IO write requests and their corresponding data to disk during the burst workload; and
compress the data during a data compression self-healing period after a delay period, wherein the delay period is after the identified burst workload, and wherein the data compression self-healing period is a period when the storage array has available resources to perform compression operations on the temporarily stored uncompressed data, and wherein the data compression self-healing period is specifically triggered by detecting that the storage array has transitioned from a high resource utilization state during the burst workload to a lower resource utilization state with sufficient processing capacity available for background compression operations.

### Claim 12 (depends on 11)

The apparatus of claim 11, further configured to:
define a duration of the delay period based on an availability of storage array resources.

### Claim 13 (depends on 11)

The apparatus of claim 11, further configured to:
define a start and duration of the self-healing period based on available idle resource utilization of the storage array, wherein the available idle resource utilization represents unused processing capacity of the storage array.

### Claim 14 (depends on 11)

The apparatus of claim 11, further configured to:
determine a compressibility of the data corresponding to each IO write operation in the burst workload; and
apply adaptive compression algorithms to the data based on the determined compressibility of the data.

### Claim 15 (depends on 14)

The apparatus of claim 14, further configured to:
select between light compression and heavy compression based on a current load of the storage array and the compressibility of the data, wherein the storage array's current load refers to the level of resource utilization of the storage array at a given time.

### Claim 16 (depends on 11)

The apparatus of claim 11, further configured to:
identify the burst workload by calculating a Burst Heat Index (BHI) for each storage group in the storage array based on a score biased towards IO write operations.

### Claim 17 (depends on 16)

The apparatus of claim 16, further configured to:
identify each storage group targeted by IO operations in the burst workload using the BHI.

### Claim 18 (depends on 11)

The apparatus of claim 11, further configured to:
identify an IO signature of the IO operations received by the storage array.

### Claim 19 (depends on 18)

The apparatus of claim 18, further configured to:
determine whether the IO signature of the IO operations matches an IO shapelet defining a burst workload type.

### Claim 20 (depends on 19)

The apparatus of claim 19, further configured to:
define a burst workload type based on a threshold of IOPS received by the storage array during a time window threshold.
