Cache Refresh with a Single Indicator for Peak Load Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Caching data in computer systems leads to resource usage spikes during peak hours due to stale data refresh, which is costly and complex to manage, especially for daily users accessing systems at the same time.

Innovation Solution

Implement a single refresh indicator to proactively refresh cached data during non-peak times, using a method that includes setting the indicator to 'true' upon user access, refreshing data during off-peak hours, and resetting it after refresh, thus ensuring data availability without resource spikes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cache refresh happens on demand when data becomes stale, then data freshness is maintained, but resource usage spikes during peak hours

Engineering Contradiction:
Improvedata freshnessVSAvoidresource usage
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

The system performs cache refresh in advance during non-peak hours by setting a refresh indicator when data is accessed, then automatically refreshing the cache during off-peak times before the next peak usage period. This preliminary action prevents the resource spike that would occur if refresh waited until data became stale during peak hours.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If automatic refresh is implemented to prevent stale data, then data freshness is improved, but system complexity and cost increase

Engineering Contradiction:
Improvedata freshnessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts only the essential refresh indicator flag from the cache data structure, separating the refresh management logic from the main data storage. This minimal extraction allows automatic refresh functionality without requiring complex tracking systems, counters, or additional metadata structures that would increase system complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

3Power

If pro-active refresh is implemented to spread resource usage, then peak load is reduced, but tracking complexity increases

Engineering Contradiction:
Improveresource usage distributionVSAvoidtracking complexity
Core Design Contradiction:
PowerVSDevice complexity

Solution Approach 1:

The cache data structure serves itself by including an embedded refresh indicator that automatically triggers the refresh process. The system uses the cache's own state (the indicator flag) to manage its own refresh timing, eliminating the need for external tracking systems, counters, or complex scheduling mechanisms.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12423000B2Cache refresh system and processes
Publication Date: 2025.09.23 ADP INC
  • US12423000B2 patent drawing
  • US12423000B2 patent drawing
  • US12423000B2 patent drawing

AI summary

The present disclosure relates generally to computer systems and, more particularly, to a cache refresh system and related processes and methods of use. The method of refreshing data in cache memory includes: setting, by a computer system, a refresh indicator to “true”; refreshing data in the cache memory, by the computer system, upon a determination that the refresh indicator is set to “true”; and setting, by the computer system, the refresh indicator to “false” after the refreshing of the cache memory.