Caching Management via Dummy File Eviction Probing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current caching management systems fail to optimally determine which content to cache and when, leading to inefficient use of cache space due to static decisions and lack of coordination between content providers and cache servers, resulting in new hot content not being cached in time and old cold content occupying space.

Innovation Solution

A caching management method that involves embedding a notification request tag in a dummy file, uploading it to a cache server, recording eviction timestamps, and calculating eviction time, then comparing this to the average inter-request time of actual files to determine if they should be uploaded, ensuring that only content with a shorter eviction time than average request intervals is cached.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If static caching decisions are made beforehand, then cache server capacity is predetermined, but new hot content cannot be cached in time and cold content occupies space

Engineering Contradiction:
Improveadaptability to changing access patternsVSAvoidcaching management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by uploading dummy files before actual content to probe cache eviction behavior. This advance probing allows the system to predict cache retention times and make informed decisions about whether to upload actual content, thereby adapting to cache dynamics without complex real-time management.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by monitoring eviction notifications and using the observed eviction times to dynamically adjust caching decisions. The eviction time information feeds back into the upload decision logic, allowing the system to adapt to changing cache server behavior and access patterns automatically.

Inventive Principle:
Principle #23Feedback

2Quantity of substance

If cache server capacity is fixed, then resource allocation is simple, but cache space is wasted when evicting content due to capacity limits

Engineering Contradiction:
Improvecache space utilizationVSAvoidcontent eviction time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

By uploading dummy files in advance and measuring their eviction times, the system gains foresight into cache server behavior. This preliminary probing enables the system to predict whether actual content will be retained or evicted, allowing for optimized upload decisions that maximize cache space utilization while minimizing premature evictions.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses the cache server's own eviction mechanism and timing behavior to inform caching decisions. By observing how the cache server naturally evicts content and using this information to guide upload decisions, the system effectively makes the cache server serve its own optimization needs without external intervention.

Inventive Principle:
Principle #25Self-service

3Speed

If content is pushed to cache servers without coordination, then content delivery latency is reduced, but cache space is inefficiently used

Engineering Contradiction:
Improvecontent delivery speedVSAvoidcache space efficiency
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The system establishes coordinated feedback between content provider and cache server by monitoring eviction notifications. This feedback loop allows the content provider to understand cache retention patterns and make intelligent decisions about what content to push, ensuring that cached content remains in the cache long enough to be useful while maximizing cache space efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary eviction time measurement using dummy files before pushing actual content. This advance measurement allows the system to predict cache retention duration and only push content that is likely to be retained, thereby improving both content delivery speed and cache space efficiency through coordinated decision-making.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If eviction time is short, then cache turnover is fast, but content may be evicted before being accessed

Engineering Contradiction:
Improvecache turnover rateVSAvoidcontent accessibility
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system performs preliminary measurement of eviction times using dummy files to establish baseline cache retention characteristics. This advance knowledge allows the system to compare against inter-request times and only cache content that is likely to be accessed before eviction, thereby maintaining high cache turnover rates while ensuring content accessibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from observed eviction times to dynamically adjust caching decisions. By continuously monitoring how long cached content remains before eviction and comparing this against actual access patterns, the system can adapt its caching strategy to maintain reliability while preserving healthy cache turnover.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10225361B2Content management in caching services
Publication Date: 2019.03.05 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10225361B2 patent drawing
  • US10225361B2 patent drawing
  • US10225361B2 patent drawing

AI summary

A caching management method includes embedding a notification request tag in a dummy file, uploading the dummy file to a cache server, recording a timestamp indicating a first point in time that the dummy file is uploaded to the cache server, receiving an eviction notification indicating a second point in time that the dummy file is evicted from the cache server, and calculating an eviction time indicating an amount of time taken for the dummy file to be evicted from the cache server. Transmission of the eviction notification is triggered in response to processing the notification request tag, and the dummy file is not retrieved from the cache server between the first point in time and the second point in time. The eviction time is equal to a difference between the first point in time and the second point in time.