Knowledge Base Snapshot via Copy-on-Write Virtual Memory
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing knowledge base systems face challenges in saving large, complex data sets to disk without incurring significant overhead or disrupting system operations, as linearizing and writing such data is time-consuming and may require stopping all activity or using high-overhead transaction mechanisms.
Innovation Solution
A method involving bringing the knowledge base to a consistent state, creating a copy-on-write virtual copy using virtual memory, and serializing this copy to persistent storage without blocking ongoing operations, utilizing copy-on-write virtual memory mappings and separate processes for efficient snapshotting.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the knowledge base is saved to disk by linearizing and writing the data, then a persistent copy is created, but the operation is time-consuming and blocks system activity
Solution Approach 1:
The patent creates a virtual copy of the knowledge base in memory using copy-on-write semantics before serializing it to disk. This allows the original knowledge base to remain accessible and responsive while the copy is being saved, eliminating the blocking effect on system activity.
Solution Approach 2:
The patent transitions from a single-threaded, blocking save operation to a multi-dimensional approach using separate memory spaces (original and virtual copy) and asynchronous serialization. This allows persistence operations to occur in parallel with query operations, resolving the contradiction between reliability and productivity.
2Reliability
If transaction mechanisms are used to ensure consistency during saving, then data consistency is maintained, but overhead increases significantly
Solution Approach 1:
The patent brings the knowledge base to a consistent state before creating the virtual copy, ensuring data consistency is established in advance. This preliminary action eliminates the need for complex transaction mechanisms during the save operation, reducing overhead while maintaining consistency.
Solution Approach 2:
By creating a virtual copy rather than modifying the original knowledge base during serialization, the patent ensures consistency without requiring complex transaction management. The copy-on-write mechanism automatically handles consistency, simplifying the system overhead.
3Reliability
If all activity is stopped during serialization to ensure consistency, then data integrity is preserved, but system availability is reduced
Solution Approach 1:
The patent creates a virtual copy of the knowledge base that can be serialized independently. This allows the original system to continue processing queries and updates without interruption, while the copy is being saved to disk, eliminating system downtime while preserving snapshot consistency.
Solution Approach 2:
The patent segments the knowledge base into the original operational instance and a separate virtual copy for serialization. This segmentation allows independent operation of the original system during the save process, preventing loss of time while maintaining reliability.
Data Source
AI summary
A consistent snapshot of a large main memory knowledge base is saved to persistent storage without blocking the application for the duration of serializing and writing the knowledge base. Taking the snapshot comprises bringing the knowledge base to a consistent state (in a multithreaded application), using virtual memory facilities to obtain a copy-on-write copy of the knowledge base in memory, and using a separate thread or process to serialize the copy-on-write copy to persistent storage.