Client File Cache Management via Usage History
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client application file caches on devices accumulate old or obsolete files, leading to storage space issues and inefficiencies in retrieving desired files, as existing management methods rely on inaccurate timestamp-based approaches or fail to differentiate between important and unused files.
Innovation Solution
Implement a system where files used during previous runs are identified and retained in a 'keep set' while unused files are removed, using a history file to determine importance and avoiding timestamp-based deletion, allowing for efficient cache management and recovery from corrupted files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If files are retained in the file cache for later retrieval, then file access speed is improved, but the cache accumulates old or obsolete files causing storage space to be wasted
Solution Approach 1:
The system automatically identifies and removes obsolete files from the cache while preserving frequently accessed files. The cache management system discards files that are no longer needed (obsolete files) and recovers storage space, while maintaining fast access to active files through intelligent retention policies based on file age, access patterns, and cache configuration.
Solution Approach 2:
The file cache system performs self-management by automatically identifying which files to retain and which to remove without requiring manual intervention. The cache management mechanism monitors file usage patterns, determines obsolescence based on multiple criteria (age, access frequency, configuration rules), and autonomously cleans up the cache to maintain optimal performance and storage utilization.
2Extent of automation
If timestamp-based approaches are used to manage file cache, then automation is improved, but measurement precision deteriorates due to inaccurate timestamps
Solution Approach 1:
The system uses multiple feedback mechanisms to determine file importance and obsolescence. Instead of relying solely on potentially inaccurate timestamps, the system incorporates access patterns, file usage history, and configuration rules as feedback signals. This multi-criteria feedback approach provides more precise determination of which files to retain or remove, improving measurement precision while maintaining automation.
3Reliability
If all files are retained in the cache, then file availability is improved, but retrieval efficiency deteriorates due to excessive cache size
Solution Approach 1:
The system applies different retention qualities to different files based on their characteristics and usage patterns. Frequently accessed or important files are retained in the cache with high availability, while obsolete or rarely used files are removed. This local differentiation of file quality and retention policy maintains high retrieval efficiency by keeping the cache size manageable while ensuring file availability for files that actually need to be accessed.
Data Source
AI summary
A method, a system, and an article are provided for managing a file cache for a client application. An example computer-implemented method can include: storing a plurality of files in a memory on a client device for a client application; identifying a first portion of the files in the memory as having been used during a previous run of the client application; receiving, from at least one server, one or more lists of files to be used during a current run of the client application; identifying a second portion of the files in the memory as not being included in at least one of the first portion and the one or more lists of files from the at least one server; and removing, from the memory, at least a subset of the second portion of the files during the current run of the client application.