Device quick startup method, system, terminal and readable storage medium

Abstract

The present invention relates to the field of computer technology, and discloses a method, system, terminal and readable storage medium for rapid device startup, the method comprising: starting an operating system, recording the operating system startup process, and obtaining record data; analyzing the record data to obtain analysis data; and determining the startup scheme of the operating system according to the analysis data. The present invention records the startup situation during the system startup process, analyzes the record, and adjusts the original startup scheme according to the analysis result. Compared with the previous manually adjusted scheme, the present invention can automatically adjust according to the data of each user when the system is started, has good compatibility, and can be popularized.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a device quick startup method, system, terminal and readable storage medium. Background Art

[0002] During the current system startup process, various firmwares are loaded and run, and each functional module of the processor is uniformly measured and enabled for security. Traditional system startup methods usually require loading a large number of files and data from the disk, resulting in a long startup time. Although the use of pre-reading technology can reduce the loading time, there is still a performance bottleneck. For super devices with a large number of files and data to load, this problem becomes particularly obvious.

[0003] In actual applications, different users have different requirements for processor power consumption, boot time, functional modules, etc. In this case, if unified security measurement and enabling are performed on each functional module in accordance with a unified firmware startup process, unnecessary security measurement and functional module enabling will result, thereby increasing startup power consumption and startup time.

[0004] To this end, the prior art proposes a technical solution for optimizing for different users and loading files and data in a predetermined order. However, this solution relies on manual adjustment for optimizing the user startup order. The manual adjustment not only completely relies on manual experience, but also the specific optimization basis and process are not transparent to the user, and the cost is extremely high, making it difficult to popularize. Summary of the invention

[0005] The purpose of the present invention is to provide a method, system, terminal and readable storage medium for rapid device startup, which aims to solve the problem that the prior art relies on manual optimization for different user startup schemes.

[0006] The technical solution adopted by the present invention to solve the technical problem is as follows:

[0007] The present invention provides a device quick startup method, the device quick startup method comprising:

[0008] Starting the operating system, recording the operating system startup process, and obtaining recorded data;

[0009] Perform analysis according to the recorded data to obtain analysis data;

[0010] A startup scheme of the operating system is determined according to the analysis data.

[0011] Furthermore, the recording of the operating system startup process to obtain the recorded data specifically includes:

[0012] Recording the hardware operation status during the startup of the operating system to obtain hardware operation data;

[0013] Record the file loading status during the startup of the operating system to obtain file loading data;

[0014] The hardware operation data and the file loading data are used as the record data.

[0015] Furthermore, the recording of the file loading situation during the startup of the operating system to obtain the file loading data specifically includes:

[0016] Recording the file loading sequence, file loading start time, file loading end time, file access relationship and pre-read data of each file in the operating system startup process;

[0017] The file loading sequence, the file loading start time, the file loading end time, the file access relationship and the pre-read data of each file are used as the file loading data.

[0018] Further, the analyzing the recorded data to obtain the analyzed data specifically includes:

[0019] Analyze the hardware operation data to obtain hardware performance bottleneck information;

[0020] Analyze the file loading data to obtain the file dependency relationship of each file and the file loading time of each file;

[0021] Obtaining hardware resource occupancy data of each of the files according to the hardware operation data and the file loading data;

[0022] The hardware performance bottleneck information, as well as the hardware resource usage data of each of the files, the file dependencies and the file loading time are used as the analysis data.

[0023] Furthermore, the analyzing according to the file loading data to obtain the file dependency relationship of each file and the file loading time of each file specifically includes:

[0024] Analyze according to the file loading sequence and the file access relationship to obtain the dependency relationship of each file;

[0025] An analysis is performed based on the file loading start time and the file loading end time of each file to obtain the file loading time of each file.

[0026] Furthermore, obtaining the hardware resource occupancy data of each file according to the hardware operation data and the file loading data specifically includes:

[0027] According to the file loading start time and the file loading end time of each file, obtain the hardware resource occupancy time period of each file;

[0028] The hardware resource occupancy data of each file is obtained by analyzing the hardware resource occupancy time periods and the hardware operation data.

[0029] Further, determining a system startup plan based on the analysis data specifically includes:

[0030] According to the dependencies between the files, a file loading order constraint is formed;

[0031] According to the hardware performance bottleneck information and the hardware resource usage data, forming file parallel loading constraints;

[0032] The system startup plan is determined according to the file loading sequence constraint and the file parallel loading constraint.

[0033] In addition, to achieve the above-mentioned purpose, the present invention also provides a device quick startup system, the device quick startup system comprising:

[0034] A data recording module is used to start the operating system, record the operating system startup process, and obtain recorded data;

[0035] A data analysis module, used to analyze the recorded data to obtain analysis data;

[0036] A scheme determination module is used to determine a startup scheme of the operating system based on the analysis data.

[0037] In addition, to achieve the above-mentioned purpose, the present invention also provides a terminal, which includes: a memory, a processor, and a device quick startup program stored in the memory and executable on the processor, and when the device quick startup program is executed by the processor, the terminal is controlled to implement the steps of the device quick startup method as described above.

[0038] In addition, to achieve the above-mentioned purpose, the present invention also provides a readable storage medium, wherein the readable storage medium stores a device quick startup program, and when the device quick startup program is executed by a processor, the steps of the device quick startup method described above are implemented.

[0039] The present invention adopts the above technical solution to achieve the following effects:

[0040] The present invention records the startup status during the system startup process, analyzes the record, and adjusts the original startup plan according to the analysis result. Compared with the previous manual adjustment plan, it can automatically adjust according to the data of each user at startup, has good compatibility, and can be popularized. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a flowchart of the steps of a method for quickly starting a device in a preferred embodiment of the present invention;

[0042] Figure 2 It is a structural schematic diagram of a device quick start system in a preferred embodiment of the present invention;

[0043] Figure 3 It is a schematic diagram of the operating environment of a preferred embodiment of the terminal of the present invention. DETAILED DESCRIPTION

[0044] In order to make the purpose, technical solution and advantages of the present invention clearer and more specific, the present invention is further described in detail with reference to the accompanying drawings and examples. It should be understood that the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments. The specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention. All other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0045] Example 1

[0046] See also Figure 1 , Embodiment 1 of the present application is a method for quickly starting a device, which comprises the steps of:

[0047] S1. Start the operating system, record the startup process of the operating system, and obtain record data.

[0048] In this embodiment, according to the startup flow of the operating system, the system startup process is divided into multiple key stages, and the key stages include initialization, boot loader loading, operating system kernel loading, driver loading and application startup.

[0049] Among them, initialization is the stage of initializing the hardware after the system is powered on, performing self-test and configuration to start device selection and system booting. The boot loader loading stage is the stage of loading and executing the boot loader, which is responsible for loading the operating system kernel. The operating system kernel loading stage is the boot loader loading the operating system kernel into the memory, performing kernel initialization, and configuring basic functions such as memory management and process management. The driver loading stage is to load and initialize the device driver, identify and configure all hardware components in the system, and make the hardware devices available. The application startup stage is to start user-level applications and services, and initialize the user interface and background services.

[0050] The recorded operating system startup process includes recording the start time and end time of each key stage, and monitoring the hardware operation status and recording file loading status at each stage for subsequent analysis and use.

[0051] The hardware operation status detection includes central processing unit (CPU) monitoring, memory monitoring and disk I / O (input / output) monitoring.

[0052] Among them, CPU monitoring uses CPU hardware performance counters (Hardware Performance Counter) to count various events, such as the number of instruction executions, cache hit rate, etc., so that CPU usage can be monitored in a very fine-grained manner, including the time distribution of user state and kernel state, function call graph, etc. The CPU usage is obtained by reading and parsing the hardware performance counter file, and the analysis can provide information such as CPU utilization, context switching times, and interrupt number.

[0053] Memory monitoring refers to monitoring memory access by tracking events such as page tables, page faults, and cache hits. Through monitoring, information such as memory access patterns, cache hit rates, memory allocation and release can be captured to help analyze memory performance and optimize problems. In this embodiment, memory usage is obtained by reading a memory monitoring file. It can provide information such as the total amount of memory, free space, and cache and buffer usage.

[0054] I / O monitoring uses I / O event tracking to monitor the number, latency, and throughput of disk read and write operations. It can identify hot spots in disk I / O and help find disk performance bottlenecks. It can monitor disk I / O conditions and provide information such as the read and write rate, request queue length, and average response time of each disk device.

[0055] Recording the file loading status includes recording the file loading sequence, file loading start time, file loading end time, file access relationship and pre-read data of each file.

[0056] Among them, regarding pre-read data, the existing technology, when loading files, will adopt pre-loading technology according to a predetermined loading order, and load the data in the pre-read cache area of ​​each loading stage to the corresponding target location, so as to reduce the time of loading from the disk, and finally achieve fast startup of the system, and obtain the pre-read data of the file, that is, to obtain the data in the pre-read cache area read when the file is loaded.

[0057] S2. Analyze the recorded data to obtain analysis data.

[0058] Specifically, in this embodiment, the hardware operation status is analyzed to obtain the bottleneck points and performance bottlenecks in the system startup process, so as to guide the subsequent optimization work.

[0059] The loading time of each file is obtained according to the file loading start time and file loading end time analysis, and the usage of hardware resources during the file loading process is analyzed. The file loading time and the usage of hardware resources at each time are correlated and analyzed to determine the hardware resource usage data when each file is loaded, and the CPU intensive tasks in the startup process are determined according to the hardware resource usage data, and the corresponding files are divided into CPU intensive files, so that when parallel loading is performed later, the corresponding files can be divided into high-performance CPUs for loading, so as to optimize CPU resource allocation and improve startup efficiency.

[0060] In addition, file dependencies are also divided according to the file loading situation to determine the file dependencies. File dependencies refer to the fact that the operation of some files depends on other files, and other files must be loaded before they can be loaded, such as driver dependencies and system service dependencies. Driver dependencies, such as graphics card drivers depend on kernel modules, and sound card drivers depend on basic audio drivers; system service dependencies, such as network services depend on network drivers, and file system services depend on disk drivers.

[0061] In this embodiment, file dependencies are obtained through an analysis tool. In this embodiment, the analysis tool obtains file dependencies in the following ways: monitoring system logs, tracking system calls, static analysis, and dynamic analysis. Among them, the monitoring system is determined to analyze the file loading order and dependencies during the system startup process by reading the system log file. Tracking system calls refers to using the system call tracking tool to record all file accesses and dependencies during the system startup process. Static analysis refers to analyzing configuration files and startup scripts to determine the files and dependencies that need to be loaded during the startup process. Dynamic analysis dynamically captures file loading and dependencies by simulating the system startup process.

[0062] In addition, in this embodiment, the priority of the files is adjusted according to the dependency of the files. Specifically, the priority of all files is first determined according to the importance and frequency of use. Then, the priority order is adjusted according to the dependency of the files to ensure that the pre-placed files are loaded first.

[0063] S3. Determine a system startup plan based on the analysis data.

[0064] Specifically, in this embodiment, the preliminary file loading order can be first determined according to the priority, and then a parallel loading plan can be formed according to the file loading order. The parallel loading plan is then adjusted according to the recorded data and the analyzed data to determine whether the high-performance CPU can meet the simultaneous loading of CPU-intensive files in all time periods. If not, the loading order of the CPU-intensive files is adjusted to prevent performance bottlenecks. The loading order of parallel files is then adjusted according to the hardware operating conditions. Specifically, the difference between the performance bottleneck in each time period and the performance required by the file can be used as a judgment condition. If the difference is too large, it indicates that the file loading order needs to be adjusted to reduce the loading time.

[0065] The performance bottleneck can also be used as a constraint and goal. While ensuring that the performance bottleneck is not exceeded, the loading is performed as close to the performance bottleneck as possible. The goal is to minimize the integral of the sum of the performance bottleneck and the hardware resource usage data of the file in each time period. The performance bottleneck and file dependency are used as constraints to solve the strategy and obtain the final system startup plan. Among them, the performance bottleneck includes both the bottleneck of CPU usage and the performance bottleneck of memory and hard disk usage caused by preloading technology. The difference between each performance bottleneck and the required performance needs to be quantified and weighted. The specific quantification method and weighting parameters can be set according to actual needs.

[0066] Similarly, a problem can be solved based on the file loading time of each file with the goal of minimizing the total loading time, with constraints formed by the hardware resource usage data and performance bottlenecks of each file, and constraints formed by file dependencies, to solve the problem and obtain the final system startup solution.

[0067] The present invention provides a more complete and detailed intelligent system startup optimization method by refining the steps of the original intelligent system startup solution and adding new steps. The intelligent analysis tool is used to analyze the system startup process in detail, so that the loading order of files can be determined more accurately, with a more precise file loading order, and the startup time can be minimized. By realizing the parallel loading of multiple files, hardware resources can be fully utilized to improve the loading efficiency. According to the monitored performance data and startup time, the loading strategy can be flexibly adjusted to adapt to different systems and startup conditions, and the startup speed of the system can be further improved. The intelligent analysis tool is used to identify the dependency relationship in the system startup process, and the relevant data is loaded into the pre-read cache area in advance, so that unnecessary pre-reading can be avoided. , improve pre-reading efficiency and reduce disk loading time. According to the results of the intelligent analysis tool, the data content and size of the pre-read cache area are further optimized to ensure that the most commonly used and important files and data can be pre-read and cached, thereby further accelerating the system startup speed. It also has an adaptive adjustment function. By monitoring system performance and startup time, the intelligent analysis tool can dynamically adjust the loading strategy, pre-reading range and cache area configuration to adapt to different hardware configurations and startup environments, further improving the system startup speed. The method and device can be applied to various computer systems, including personal computers, servers, and embedded devices. At the same time, it is also scalable and can cope with the growing system startup needs and the ever-changing technical environment.

[0068] Example 2

[0069] See also Figure 2 Based on the above method, the present invention also provides a device quick start system, the device quick start system comprising:

[0070] The data recording module 51 is used to start the operating system, record the operating system startup process, and obtain recorded data.

[0071] Further, the recording of the operating system startup process to obtain the recorded data specifically includes:

[0072] Recording the hardware operation status during the startup of the operating system to obtain hardware operation data;

[0073] Record the file loading status during the startup of the operating system to obtain file loading data;

[0074] The hardware operation data and the file loading data are used as the record data.

[0075] Furthermore, the recording of the file loading situation during the startup of the operating system to obtain the file loading data specifically includes:

[0076] Recording the file loading sequence, file loading start time, file loading end time, file access relationship and pre-read data of each file in the operating system startup process;

[0077] The file loading sequence, the file loading start time, the file loading end time, the file access relationship and the pre-read data of each file are used as the file loading data.

[0078] A data analysis module 52, used to analyze the recorded data to obtain analysis data;

[0079] Further, the analyzing the recorded data to obtain the analyzed data specifically includes:

[0080] Analyze the hardware operation data to obtain hardware performance bottleneck information;

[0081] Analyze the file loading data to obtain the file dependency relationship of each file and the file loading time of each file;

[0082] Obtaining hardware resource occupancy data of each of the files according to the hardware operation data and the file loading data;

[0083] The hardware performance bottleneck information, as well as the hardware resource usage data of each of the files, the file dependencies and the file loading time are used as the analysis data.

[0084] Furthermore, the analyzing according to the file loading data to obtain the file dependency relationship of each file and the file loading time of each file specifically includes:

[0085] Analyze according to the file loading sequence and the file access relationship to obtain the dependency relationship of each file;

[0086] An analysis is performed based on the file loading start time and the file loading end time of each file to obtain the file loading time of each file.

[0087] Furthermore, obtaining the hardware resource occupancy data of each file according to the hardware operation data and the file loading data specifically includes:

[0088] According to the file loading start time and the file loading end time of each file, obtain the hardware resource occupancy time period of each file;

[0089] The hardware resource occupancy data of each file is obtained by analyzing the hardware resource occupancy time periods and the hardware operation data.

[0090] The scheme determination module 53 is used to determine the startup scheme of the operating system according to the analysis data.

[0091] Further, determining a system startup plan based on the analysis data specifically includes:

[0092] According to the dependencies between the files, a file loading order constraint is formed;

[0093] According to the hardware performance bottleneck information and the hardware resource usage data, forming file parallel loading constraints;

[0094] The system startup plan is determined according to the file loading sequence constraint and the file parallel loading constraint.

[0095] Example 3

[0096] See also Figure 3 Based on the above method, the present invention also provides a terminal, which includes a processor 10, a memory 20 and a display 30. Figure 3 Only some components of the terminal are shown, but it should be understood that it is not required to implement all of the components shown, and more or fewer components may be implemented instead.

[0097] In some embodiments, the memory 20 may be an internal storage unit of the terminal, such as a hard disk or memory of the terminal. In other embodiments, the memory 20 may also be an external storage device of the terminal, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, and a flash card (Flash Card) equipped on the terminal. Further, the memory 20 may also include both an internal storage unit of the terminal and an external storage device. The memory 20 is used to store application software and various types of data installed in the terminal, such as the program code of the installation terminal. The memory 20 may also be used to temporarily store data that has been output or is to be output. In one embodiment, a device quick start program 40 is stored on the memory 20, and the device quick start program 40 can be executed by the processor 10.

[0098] In some embodiments, the processor 10 may be a central processing unit (CPU), a microprocessor or other data processing chip, used to run the program code or process data stored in the memory 20, such as executing related programs of the device quick startup method.

[0099] In some embodiments, the display 30 may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, etc. The display 30 is used to display information on the terminal and to display a visual user interface. The components of the terminal communicate with each other via a system bus.

[0100] In one embodiment, when the processor 10 executes the device quick startup program 40 in the memory 20, the steps of the device quick startup method described above are implemented.

[0101] In some embodiments, the memory 20 may be an internal storage unit of the terminal, such as a hard disk or memory of the terminal. In other embodiments, the memory 20 may also be an external storage device of the terminal, such as a plug-in hard disk, a smart memory card (SmartMediaCard, SMC), a secure digital (SecureDigital, SD) card, a flash card (FlashCard), etc. equipped on the terminal. Further, the memory 20 may also include both an internal storage unit of the terminal and an external storage device. The memory 20 is used to store application software and various types of data installed in the terminal, such as the program code of the installation terminal. The memory 20 may also be used to temporarily store data that has been output or is to be output. In one embodiment, a device quick start program is stored on the memory 20, and the device quick start program can be executed by the processor 10, thereby realizing the device quick start method in the present application.

[0102] In some embodiments, the processor 10 may be a central processing unit (CPU), a microprocessor or other data processing chip, used to run the program code or process data stored in the memory 20, such as executing the device quick startup method.

[0103] Example 4

[0104] This embodiment provides a storage medium, wherein the readable storage medium stores a device quick startup program, and when the device quick startup program is executed by a processor, the steps of the device quick startup method described above are implemented.

[0105] To summarize, the present invention records the startup status during the system startup process, analyzes the records, and adjusts the original startup scheme according to the analysis results. Compared with the previous manual adjustment scheme, it can automatically adjust according to the data of each user at startup, has good compatibility, and can be popularized.

[0106] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or terminal including the element.

[0107] Of course, those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware (such as a processor, a controller, etc.) through a computer program, and the program can be stored in a computer-readable storage medium, and the program can include the processes of the above-mentioned method embodiments when executed. The storage medium can be a memory, a disk, an optical disk, etc.

[0108] It should be understood that the application of the present invention is not limited to the above examples. For ordinary technicians in this field, improvements or changes can be made based on the above description. All these improvements and changes should fall within the scope of protection of the claims attached to the present invention.

Claims

1. A device quick startup method, characterized in that: The device quick startup method comprises: Starting the operating system, recording the operating system startup process to obtain recorded data, wherein the operating system startup process is divided into a plurality of key stages, the key stages including initialization, boot loader loading, operating system kernel loading, driver loading and application startup, recording the system startup process of each key stage to obtain recorded data; Perform analysis according to the recorded data to obtain analysis data; Determining a startup scheme for the operating system based on the analysis data; The recording of the operating system startup process to obtain the recorded data specifically includes: Record the start and end times of each key phase; Recording the hardware operation status of each key stage to obtain hardware operation data; Record the file loading status of each key stage to obtain file loading data; Using the hardware operation data and the file loading data as the record data; The recording of the file loading situation of each key stage to obtain the file loading data specifically includes: Recording the file loading sequence, file loading start time, file loading end time, file access relationship and pre-read data of each file in each key stage; The file loading sequence, the file loading start time, the file loading end time, the file access relationship and the pre-read data of each file are used as the file loading data; The analyzing according to the recorded data to obtain the analysis data specifically includes: Analyze the hardware operation data to obtain hardware performance bottleneck information; Analyze the file loading data to obtain the file dependency relationship of each file and the file loading time of each file; According to the hardware operation data and the file loading data, hardware resource occupancy data of each of the files is obtained, and CPU-intensive tasks in the startup process are determined according to the hardware resource occupancy data, and the corresponding files are divided into CPU-intensive files, so that when parallel loading is performed later, the corresponding files are divided into high-performance CPUs for loading; The hardware performance bottleneck information, as well as the hardware resource usage data of each of the files, the file dependency and the file loading time are used as the analysis data; Determining a system startup plan based on the analysis data specifically includes: According to the dependencies between the files, a file loading order constraint is formed; According to the hardware performance bottleneck information and the hardware resource usage data, forming file parallel loading constraints; Determining the system startup plan according to the file loading order constraint and the file parallel loading constraint specifically includes: Adjust the parallel loading plan based on the recorded and analyzed data to determine whether the high-performance CPU can meet the requirements of loading CPU-intensive files in all time periods at the same time. If not, adjust the loading order of CPU-intensive files. The loading order of parallel files is adjusted according to the hardware operation status, and the difference between the performance bottleneck in each time period and the performance required by the file is used as the judgment condition. If the difference is too large, the file loading order is adjusted.

2. A device quick startup method according to claim 1, characterized in that: The analyzing according to the file loading data to obtain the file dependency relationship of each file and the file loading time of each file specifically includes: Analyze according to the file loading sequence and the file access relationship to obtain the dependency relationship of each file; An analysis is performed based on the file loading start time and the file loading end time of each file to obtain the file loading time of each file.

3. A device quick startup method according to claim 1, characterized in that: The obtaining of the hardware resource occupancy data of each file according to the hardware operation data and the file loading data specifically includes: According to the file loading start time and the file loading end time of each file, obtain the hardware resource occupancy time period of each file; The hardware resource occupancy data of each file is obtained by analyzing the hardware resource occupancy time periods and the hardware operation data.

4. A device quick start system, characterized in that: The device quick start system comprises: A data recording module is used to start the operating system, record the operating system startup process, and obtain recorded data. The operating system startup process is divided into multiple key stages, including initialization, boot loader loading, operating system kernel loading, driver loading, and application startup. The system startup process of each key stage is recorded to obtain recorded data. A data analysis module, used to analyze the recorded data to obtain analysis data; A scheme determination module, used to determine a startup scheme of the operating system according to the analysis data; The recording of the operating system startup process to obtain the recorded data specifically includes: Record the start and end times of each key phase; Recording the hardware operation status of each key stage to obtain hardware operation data; Record the file loading status of each key stage to obtain file loading data; Using the hardware operation data and the file loading data as the record data; The recording of the file loading situation of each key stage to obtain the file loading data specifically includes: Recording the file loading sequence, file loading start time, file loading end time, file access relationship and pre-read data of each file in each key stage; The file loading sequence, the file loading start time, the file loading end time, the file access relationship and the pre-read data of each file are used as the file loading data; The analyzing according to the recorded data to obtain the analysis data specifically includes: Analyze the hardware operation data to obtain hardware performance bottleneck information; Analyze the file loading data to obtain the file dependency relationship of each file and the file loading time of each file; Obtaining hardware resource occupancy data of each of the files according to the hardware operation data and the file loading data; Determine the CPU-intensive tasks during the startup process based on the hardware resource usage data, and classify the corresponding files as CPU-intensive files, so that when the subsequent parallel loading is performed, the corresponding files can be divided into high-performance CPUs for loading; The hardware performance bottleneck information, as well as the hardware resource usage data of each of the files, the file dependency and the file loading time are used as the analysis data; Determining a system startup plan based on the analysis data specifically includes: According to the dependencies between the files, a file loading order constraint is formed; According to the hardware performance bottleneck information and the hardware resource usage data, forming file parallel loading constraints; Determining the system startup plan according to the file loading order constraint and the file parallel loading constraint, specifically including: Adjust the parallel loading plan based on the recorded and analyzed data to determine whether the high-performance CPU can meet the requirements of loading CPU-intensive files in all time periods at the same time. If not, adjust the loading order of CPU-intensive files. The loading order of parallel files is adjusted according to the hardware operation status, and the difference between the performance bottleneck in each time period and the performance required by the file is used as the judgment condition. If the difference is too large, the file loading order is adjusted.

5. A terminal, characterized in that: The terminal includes: a memory, a processor, and a device quick startup program stored in the memory and executable on the processor. When the device quick startup program is executed by the processor, the terminal is controlled to implement the steps of the device quick startup method as described in any one of claims 1 to 3.

6. A readable storage medium, characterized in that: The readable storage medium stores a device quick startup program, and when the device quick startup program is executed by a processor, the steps of the device quick startup method according to any one of claims 1 to 3 are implemented.

Images