Snapshot File Loading Sequence for Faster Application Startup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information processing systems face delays in startup times due to overlapping periods for loading applications and snapshot files from non-volatile storage into RAM, leading to increased waiting times and reduced efficiency.
Innovation Solution
The system loads the snapshot file into RAM before loading the operating system, utilizing a read program that operates independently of the OS to reduce bus usage conflicts and expedite the startup process by separating the loading periods of applications and snapshot files.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the snapshot file is loaded into RAM after the operating system is loaded, then the system can use the standard OS loading procedure, but the startup time is increased due to overlapping loading periods
Solution Approach 1:
The snapshot file is loaded into RAM before the operating system is loaded, which is a preliminary action that prepares the restoration data in advance. This allows the application to be restored quickly once the OS is ready, reducing the overall startup time while maintaining a manageable loading sequence through the use of a read program that operates independently of the OS.
2Productivity
If the application program and snapshot file are loaded simultaneously from non-volatile storage, then the loading process is efficient, but bus usage conflicts increase causing waiting time
Solution Approach 1:
The loading process is segmented into two distinct phases: first, the snapshot file is loaded using a dedicated read program before the OS loads; second, the application program is loaded after the OS is running. This segmentation eliminates bus usage conflicts that would occur if both files were loaded simultaneously, as each loading operation occurs in a separate time window with dedicated bus access.
3Loss of time
If a read program operates independently of the OS to load the snapshot file, then bus usage conflicts are reduced, but the system requires additional program logic
Solution Approach 1:
A read program acts as an intermediary between the non-volatile storage and the snapshot file, handling the loading operation independently of the operating system. This intermediary component simplifies the overall system architecture by separating the snapshot loading function from the OS loading process, reducing bus conflicts without requiring complex coordination logic between multiple components.
Data Source
AI summary
In an information processing apparatus, a snapshot file corresponding to an application program is read from a non-volatile storage medium and the read snapshot file is loaded into a RAM. An operating system on which the application program operates is loaded into the RAM, and the operating system is started. The application program is read from the non-volatile storage medium after starting the operating system; the read application program is loaded into the RAM. The application program loaded in the RAM is started by using the snapshot file loaded in the RAM. Herein, reading the snapshot file from the non-volatile storage medium and loading the read snapshot file into the RAM are performed (i) before loading the operating system on which the application program operates into the RAM, or (ii) while performing a process of starting the operating system.