Database File Write-Back Using Low-Frequency Update Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database update methods suffer from bottlenecks due to repeated writing to slower secondary storage devices, which prolong the time required for database updates when multiple updates are performed in the same nonvolatile memory area.
Innovation Solution
A method and apparatus that involve copying files from a first storage device to a second storage device, identifying files with low writing frequency, and writing them back to the first storage device, utilizing query determination, low-frequency file identification, and write-back processes to optimize database updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is repeatedly written to the secondary storage device every time an update is performed, then the database can be kept up-to-date, but the writing speed becomes a bottleneck and update time increases significantly
Solution Approach 1:
The patent applies preliminary action by copying files from the first storage device to the second storage device before actual updates are performed. This allows the system to prepare data in advance in the faster first storage device, so that when updates are needed, they can be performed there without immediately writing to the slower second storage device, thus reducing update time while maintaining data accuracy
Solution Approach 2:
The patent introduces the second storage device as an intermediary between the database system and the final storage. Updates are performed on copied files in the second storage device, and only necessary changes are written back to the first storage device. This intermediary layer acts as a buffer that decouples the frequent update operations from the slower persistent storage, resolving the time bottleneck
2Reliability
If all updated files are written back to the first storage device, then data consistency is maintained, but writing frequency increases and time is lost
Solution Approach 1:
The patent extracts only the necessary update operations from the full set of file operations. By identifying and applying only the essential changes to the original files in the first storage device, rather than rewriting entire files or all updated files, the system maintains data consistency while significantly improving update efficiency and reducing writing frequency
Solution Approach 2:
The patent changes the parameter of writing frequency by introducing selective write-back based on update necessity. Instead of writing back all updated files with equal frequency, the system adjusts writing frequency based on actual update needs, transforming the rigid write-all approach into a flexible selective write approach that improves productivity while maintaining consistency
Data Source
AI summary
An update method in which a computer updates data stored in a first storage device by copying a plurality of files stored in the first storage device to a second storage device and writing the files updated in the second storage device back to the first storage device, the plurality of files constituting a part of a database. The update method includes a query determination for determining whether a query for requesting writing to one of the files stored in the second storage device is based on a cluster key of the database, low-frequency file identification for identifying a file having a low writing frequency among the files stored in the second storage device, and write-back for writing the file having the low writing frequency identified in the low-frequency file identification to the first storage device.