JP5335625B2 - Computer program that reduces boot time - Google Patents

Description

  The present invention relates to a technique for reducing the boot time of a computer, and more particularly to a technique for reducing the boot time when there is a program that reads a large number of files from a boot medium at the time of booting.

  When the computer is turned on, it starts a boot process (also called boot strap or boot) that reads a boot file from a boot disk or boot medium. First, an initialization program called POST (Power On Self Test) stored in the BIOS_ROM is read into the main memory and executed. The initialization program diagnoses and initializes the boot device. Next, the BIOS searches for a boot disk in which a boot file is stored. The boot file includes an operating system, device drivers, application programs, and the like. A hard disk drive (HDD) is usually used as the boot disk.

  The BIOS loads an MBR (Master Boot Record) stored in the head sector of the HDD into the main memory and transfers control to it. The MBR searches the disk for a bootable partition, loads the bootstrap loader in the first sector (boot sector) into the main memory, and transfers control to it. After that, the boot file is sequentially read into the main memory following the boot strap loader. An operating system (OS) that performs preemptive multitasking performs preemptive task switching even at boot time. The OS generates a plurality of processes and threads to read a boot file from the HDD at the time of booting.

  The OS dispatches each process to the processor using a predetermined algorithm. The dispatched process is executed for a predetermined time slice in the processor and then preempted, and the subsequent process is dispatched. As the number of processes existing increases in the second half of booting, a lot of seek time occurs in the HDD, resulting in a decrease in boot execution efficiency and a delay in boot time.

  There is a method of completing a boot in a short time by storing a single boot image in the HDD so that an unnecessary seek does not occur, but it is limited to a special OS. Also, there is a method of using an SSD (Solid State Drive) as a boot device, but there is a limit in capacity and cost. Further, there is a method of rearranging the boot files stored in the HDD so that seeks are not likely to occur by performing defragmentation. Windows (registered trademark) introduces a function called prefetch in order to shorten use time by omitting useless page faults and seeks.

  This is a function of tracing the operation of the program being booted at the time of the previous boot, checking the access status of the file to the HDD, and prefetching a predetermined file at the next boot based on the result It is. The access log is recorded for each file and stored in a predetermined directory. In each file, data of an access pattern for the HDD for each program is recorded, and the file is prefetched into the main memory based on the access log at the time of booting.

  Patent Document 1 solves the problem of delay in startup time due to an increase in the number of startup applications in order to lower the priority order of a processor resource, an I / O resource, or a memory resource of a process that starts a specific application. The invention is disclosed. Patent Document 2 detects the start of a predetermined process, measures the CPU usage rate of the entire system, and controls the stop and restart of the process based on the CPU usage rate. An invention for suppressing deterioration is disclosed.

JP 2009-517784 A JP 2007-18282 A

  At boot time, since many boot files are loaded from a single HDD into the main memory, the access frequency to the HDD becomes very high. By the way, when a specific anti-virus program (hereinafter referred to as AV program) is introduced into a computer, it can be observed that the startup time is delayed. When the AV program is loaded at a relatively early stage and starts executing, the AV program is checked for viruses during the boot period. At that time, since the AV program independently reads the boot file from the HDD and checks for viruses, the original access for loading the HDD into the execution area of the main memory for executing the program is performed. Apart from this, an access for loading the AV program into a dedicated area of the main memory for virus checking occurs.

  As described above, a number of processes for the AV program to access the HDD during the boot period occur, and the frequency with which the process for loading other boot files accesses the HDD decreases. Access conflicts cause boot time delays. In the method of controlling the stop and execution reunion of the AV program based on the CPU usage rate as in the invention of Patent Document 2, it is determined that the execution of the AV program is stopped by a computer virus when the execution is stopped. Then, there are things that warn the user and stop booting, so it can not be adopted. Furthermore, the invention of Patent Document 2 has low effectiveness for programs other than AV programs that frequently access the HDD exclusively without increasing the CPU usage rate.

  In the invention of Patent Document 1, it is necessary to select an application to be delayed in advance and set a priority order. Therefore, the application is effective for an application selected in advance by a system developer and incorporated as a system together with the OS, but it is difficult to apply to an application introduced by a user after that.

  Accordingly, an object of the present invention is to provide a computer program that shortens the boot time of a computer in which a program for reading a large amount of boot files at the time of booting exists. It is another object of the present invention to provide a computer program that can shorten the boot time without specifying a program that causes a boot delay in advance. A further object of the present invention is to provide a computer program that can shorten the boot time without stopping the operation of the program causing the boot delay. It is a further object of the present invention to provide a computer program that can make an application program operable as soon as possible at the time of booting. It is a further object of the present invention to provide a computer that implements such a computer program.

  The computer program according to the present invention shortens the time for loading a boot file from the boot medium by operating in cooperation with the OS at the time of booting. When booting is started, loading of the boot file from the boot medium to the execution area of the main memory is started. The control target program starts reading the boot file from the boot medium to the dedicated area of the main memory for a predetermined work. The execution area is a storage area for the processor to execute the boot file, and is different from a dedicated area from which the control target program reads the boot file for the work. Therefore, in the computer, in addition to the original loading of the boot file, access to the boot medium occurs for reading by the control target program, resulting in a longer boot time.

  Subsequently, the reading speed at which the control target program reads the boot file from the boot medium is measured. Based on the measured reading speed, queuing of the process generated by the control target program for reading the boot file is executed or canceled during the boot period. As a result, access to the boot medium is dynamically assigned to the process for loading the boot file into the execution area according to the read speed of the controlled program, and the boot time without stopping the controlled program process. Can be shortened. The control target program can typically be an antivirus program. The anti-virus program may warn or stop booting when the reading process is stopped at the time of booting, but in the present invention, the execution of the anti-virus program process is only delayed and not stopped during booting. There is no such problem.

  To control process queuing, a start speed threshold and a release speed threshold smaller than the start speed threshold can be set. Then, queuing of the process can be started when the reading speed becomes equal to or higher than the start speed threshold, and the queuing can be released when the reading speed falls below the release speed threshold. When the time for queuing the process of the control target program is gradually increased, the boot completion time does not change when a certain limit is exceeded. On the other hand, it is desirable to start the control target program itself as soon as possible. Therefore, the start speed threshold value and the release speed threshold value have optimum values as a state that is effective in shortening the boot completion time and has the minimum overall queuing time.

  The optimum start speed threshold can be determined by measuring the boot completion time while changing the start speed threshold in the next boot for each boot. As the start speed threshold is decreased for each boot, the boot completion time is gradually shortened. When the boot completion time is shortened to some extent, the boot time is not shortened even if the boot start speed threshold is further reduced. The starting speed threshold at this time can be set to an optimum value. Immediately before determining the optimum value, it is desirable to confirm by slightly increasing the next start speed threshold with respect to the current start speed threshold. Furthermore, the average reading speed with respect to the total amount of boot files read by the control target program before the completion of booting can be measured, and the optimum value of the start speed threshold value including the average reading speed can be determined.

  The optimum value of the start speed threshold at this time can be a value when the average reading speed becomes maximum in a range where the boot completion time does not change. Further, it is possible to determine the optimum release speed threshold by changing the release speed threshold for each boot and measuring the boot completion time. When determining the optimal start speed threshold, if a program in which the total amount of boot files read into the dedicated area first exceeds the specified value is selected in the boot file, the control target program is identified and queued at an early stage. Can be controlled. In addition, by performing normal processing that does not queue a process for which the start speed threshold is not set, only the program that generated the process for which the start speed threshold is set can be controlled without specifying the control target program in advance. Can be treated as

  According to the present invention, it is possible to provide a computer program that shortens the boot time of a computer in which a program that reads a large amount of boot files at the time of booting exists. Furthermore, according to the present invention, it is possible to provide a computer program capable of shortening the boot time without specifying a program causing a boot delay in advance. Furthermore, according to the present invention, it is possible to provide a computer program that can shorten the boot time without stopping the operation of the program causing the boot delay. Furthermore, according to the present invention, it is possible to provide a computer program that can make an application program operable as soon as possible at the time of booting. Further, according to the present invention, a computer that implements such a computer program can be provided.

It is a functional block diagram which shows the main hardware constitutions of the computer system concerning this Embodiment It is a functional block diagram which shows the structure of the program module for implement | achieving the high-speed boot concerning this Embodiment. It is a figure which shows the data structure of the internal table of a boot I / O driver, a boot I / O log, and a boot I / O data base. It is a flowchart which shows the procedure of the delay process with respect to the control object program which a boot I / O driver performs. It is a flowchart which shows the procedure of the whole process which determines the optimal value of the starting speed threshold value QST with respect to the control object program which an I / O control service performs, and the cancellation | release speed threshold value QRT. It is a flowchart which shows the procedure of the process which determines the optimal value of the starting speed threshold value QST with respect to the control object program which an I / O control service performs. It is a flowchart which shows the procedure of the process which determines the optimal value of the cancellation | release speed threshold value QRT with respect to the control object program which an I / O control service performs. It is a flowchart which shows the production | generation method of the boot completion signal by a boot completion check program.

[Computer system configuration]
FIG. 1 is a functional block diagram showing a main hardware configuration of a computer system 10 according to the present embodiment. The computer system 10 is a server or client in which an OS is installed. The computer system 10 includes a CPU 11, a main memory 13, a network card 15, an HDD 17, a liquid crystal display (LCD) 19, a BIOS_ROM 21, and the like connected to the bus 23. The HDD 17 is a boot disk that stores a boot file. Since the functions of these hardware devices are well known with respect to the present embodiment, description thereof will be omitted.

[Software configuration]
FIG. 2 is a functional block diagram showing a configuration of a program module for realizing high-speed boot according to the present embodiment. In the block diagram of FIG. 2, Windows (registered trademark) is illustrated as an operating system (OS), and only main software related to booting is shown. However, the present invention does not need to limit the OS to Windows, and can be applied to other known OSs within the scope of the idea of the present invention.

  In FIG. 2, program modules other than the I / O control service 101, the boot I / O database 103, the boot I / O log 105, the I / O driver 107, and the boot completion check program 109 (hereinafter referred to as modules). .) Is well known. Other than the AV program 53, the scan list 59, and the filter driver 65 are OS modules. The modules described above the line 102 operate in the user mode of the processor 11, and the modules described below operate in the kernel mode.

  The boot system code 51 is a program that loads a boot file from the HDD 17 as a boot disk to the execution area of the main memory 13 in order. The AV program 53 is an example of a program to be controlled that causes a delay in boot time, and execution is delayed at the time of booting according to the present invention. When booting is started and main modules of the OS are loaded, the AV program 53 is loaded at a relatively early stage and starts executing. The AV program 53 that has started execution hooks a process in which the boot system code 51 calls an API function to load a boot file from the HDD 17, and a list of boot files read by itself is stored in the scan list 59. Generate.

  Here, the boot file is data loaded into the execution area of the main memory 13 from when the computer 10 is powered on until the boot is completed. The execution area is a storage area assigned to the main memory 13 in order to execute the boot file. The AV program 53 generates a process for calling an API function for reading a boot file registered in the scan list 59. A process is an execution unit of a program. In the present invention, a thread that is a unit in which the OS allocates processing to the CPU 11 can be treated as the same meaning. The filter driver 65 is asynchronous with the timing when the boot system code 51 loads the boot file from the HDD 17 to the execution area of the main memory 13, and loads the boot file registered in the scan list 59 from the HDD 17 to the main. Read to a dedicated area of the memory 13 The dedicated area is a storage area on the main memory for the AV program 53 to work.

  The AV program 53 performs a virus check on the boot file read into the dedicated area. Therefore, the AV program 53 accesses the HDD 17 for virus checking and sequentially loads the same boot file separately from the boot system code 51 loading the boot file into the execution area of the main memory 13. This causes a boot delay to read. In the present invention, the number of control target programs executed at the time of booting is not necessarily one, and there may be a plurality of programs that make a large number of read requests to the HDD 17 independently.

  The Kernel32.dll 55 is a part of the Windows (registered trademark) subsystem DLL (Dynamic Link Library), and converts a public Windows API function into a call to a private kernel mode system service. For example, when a previously loaded boot file calls a function open to an application called ReadFile API in order to read the next boot file from the HDD 17 to the main memory 13, a non-public Ntoskrnl 63 responds accordingly. An internal function called NtReadFile is called to load data from the HDD 17.

  Ntdll.dll 57 is a support library that provides a function for using the subsystem DLL. Ntdll.dll 57 includes an interface function (System Service Dispatch Stub) that can be called from the user mode, and an internal support function such as an NtReadFile function used by the subsystem DLL. The Ntoskrnl 63 includes an internal function executed in the kernel mode, a system service dispatcher, an interrupt dispatch table, and the like. The file system 67 is software provided by the OS for managing data stored in the HDD 17. The file system 67 creates a FAT (File Allocation Table) and a directory, and manages recording, reading, deleting, moving, and the like of files related to the HDD 17.

  The OS cache manager 69 is software provided by the OS in order to improve the performance of access to the HDD 17. The OS cache manager 69 prefetches and fills data in the OS cache area so that the HDD 17 can be processed without accessing the HDD 17 each time the ReadFile API function or the WriteFile API function is called. The OS cache manager 69 manages access to the HDD 17 from all software executed by the computer 10 and manages file filling and flushing to the OS cache area based on a unique algorithm. The disk driver 71 is software for controlling the operation and data transfer of the HDD 17. The OS Shell Startup 61 is a program for automatically starting (AutoRun) a program registered in the registry at the time of booting.

  The I / O control service 101 sets a threshold for queuing a process for the control target program to make a read request to the HDD 17 in the boot I / O driver 107, and determines an optimum threshold. It is. The boot I / O data base 103 is a file for registering an optimum threshold value for each process of a control target program that reads a boot file. FIG. 3C shows the data structure of the boot I / O data base 103. The boot I / O data base 103 includes a start speed threshold QST that is an optimum threshold for starting queuing for each process of the control target program, and a release speed threshold QRT that is an optimum threshold for releasing queuing, respectively. An optimization completion flag indicating that is set can be registered. As an example, FIG. 3C shows that an optimum start speed threshold value QST and an optimum release speed threshold value QRT are registered for the process A, and only an optimum start speed threshold value QST is registered for the process B. Indicates that no threshold is registered.

The boot I / O log 105 is queued by the boot I / O driver 107 for each boot until the I / O control service 101 determines the optimum threshold for the process in which the control target program reads the boot file. Tentative start speed threshold value QST, release time threshold value QRT, boot completion time BCT until boot is completed, and average read speed AVR with respect to the total number of bytes of the boot file read by the process of the control target program until boot completion Is a file to record. FIG. 3B shows the data structure of the boot I / O log 105. In FIG. 3B, as an example, when the number of boots is 7 for process A, the start speed threshold value QST is changed from V ₀ as the initial value to V _n as the optimum value from 1 to 4 times. to change, release speed threshold QRT a value obtained by subtracting a constant value beta ₀ from the start speed threshold QST is recorded.

An optimum start speed threshold value QST is determined as V _{n at} the time of the fourth boot. Until 4-7 times, release velocity threshold QRT to decrement β is subtracted a variable for the optimal starting velocity threshold QST is recorded, recorded as the optimal release velocity threshold QRT is S _n at 7 th boot Has been. The boot I / O driver 107 is a program that queues a process of a control target program that reads a boot file and delays execution. The boot I / O driver 107 queues the process based on the provisional or optimum start speed threshold value QST and release speed threshold value QRT set by the I / O control service 101.

  The boot I / O driver 107 has an internal table. FIG. 3A shows the data structure of the internal table 121. The internal table includes a process name for each process of the control target program, a boot file read speed CVR currently read by the process of the control target program, a queuing execution flag, a start speed threshold QST for starting queuing, and queuing The release speed threshold QRT for canceling and the average reading speed AVR measured by the boot I / O driver 107 are recorded. As an example, the current reading speed CVR is the number of bytes of the boot file read out per second. The internal table 121 also temporarily records the process name of the program other than the control target program and the current reading speed CVR.

  The boot completion check program 109 is registered in the registry of the OS Shell Startup 61 and is automatically started at boot time. The boot completion check program 109 detects the boot completion state of the computer 10, sends a boot completion signal to the I / O control service 101, measures the boot completion time, and records it in the boot I / O log 105. It is a program. The configuration of the program module in FIG. 2 described above is an example, and the illustrated module can be integrated or divided within the scope of the present invention. The module shown in FIG. 2 is loaded into the main memory 13 and executed by the CPU 11, thereby causing the computer 10 to realize a predetermined function.

[Procedure for delayed processing of controlled programs]
FIG. 4 is a flowchart showing the procedure of the delay process for the control target program executed by the boot I / O driver 107. In block 201, as described in the procedure of FIGS. 5 to 7, the I / O control service 101 tentatively determines the optimum threshold value for the process of the control target program in the registry of the boot I / O driver 107. A start speed threshold value QST and a release speed threshold value QRT are set. Note that, as will be described with reference to FIG. 6, until the I / O control service 101 determines the optimum start speed threshold value QST for the process that requests reading, the program is treated as a control target program candidate.

When the computer 10 is powered on, control is transferred from the BIOS to the OS, and the boot file is loaded in order. When the boot system code 51 starts to operate, the OS Shell Startup 61 automatically starts the boot completion check program 109. The boot completion check program 109 is activated whenever a substantially constant time has elapsed since the activation of the power supply. The boot completion check program 109 detects the boot completion state by measuring the CPU usage rate of the entire computer. The CPU usage rate Y of the entire computer can be calculated by the following formula when the user mode time of the idle process is Ui, the kernel mode time of the idle process is Ki, and the elapsed time is Et.
Y = (1− (Ui + Ki) / Et) × 100%

  In block 203, the boot I / O driver 107 determines whether or not a process generated by a program that accesses the HDD 17 makes a read request. It should be noted that the process to be determined is not limited to the control target program, but covers all programs. If it is a process other than a read request such as a write request or a stop request, the boot I / O driver 107 causes the disk driver 71 to process. In the case of a read request process, the process proceeds to block 205 where the boot I / O driver 107 records the process name and the current read speed CVR of the process in the internal table 121 for the process. When the start speed threshold value QST and the release speed threshold value QRT are set for the process, the boot I / O driver 107 records the values in the internal table 121.

  In block 207, the boot I / O driver 107 refers to the internal table 121 and checks whether or not the queuing execution flag is on. The queuing execution flag is turned on at this boot if it passes through blocks 208, 209, 211, and 213. If the queuing in progress flag is off, the process proceeds to block 208 where the boot I / O driver 107 determines the start speed threshold QST and the release speed regardless of whether the process is a provisional value or an optimum value. It is determined whether or not a threshold QRT is set. If the threshold value is not set by the I / O control service 101, the process proceeds to block 223 to perform normal processing without queuing. When the threshold value is set, the process proceeds to block 209, and the boot I / O driver 107 has the boot file current read speed CVR read from the HDD 17 by the process equal to or higher than the start speed threshold value QST. Inspect whether or not.

  If the current read speed CVR is not equal to or higher than the start speed threshold QST, the process of the read request is passed to the disk driver 71 in block 223 without performing queuing in this boot, and normal processing is performed. If the current read speed CVR is equal to or higher than the start speed threshold QST in block 209, the boot I / O driver 107 sets a queuing execution flag in the internal table 121 in block 211, and a read request for the process in block 213. Start queuing for. The process to be queued is a process generated by a control target program or a control target program candidate, which will be described with reference to FIGS. While the process is being queued, the read request for the control target program does not pass to the disk driver 71, so that the boot file read speed read from the HDD 17 by the control target program is slow.

  Thereafter, the procedure proceeds to block 203, and after confirming the read request in block 203, the procedure proceeds to block 205 where the boot I / O driver 107 updates the current read speed CVR in the internal table 121. If the queuing execution flag of the internal table 121 is ON in block 207, the process proceeds to block 215, and the boot I / O driver 107 refers to the internal table 121 to determine whether the current reading speed CVR is the release speed threshold value. It is determined whether it is below QRT. The control target program generates a plurality of processes in order to read the boot file from the HDD 17. Since the process of the control target program after the queuing is started is delayed, the current reading speed CVR gradually decreases. Due to the queuing, the frequency of the process of the control target program accessing the HDD 17 decreases, and the access to the HDD 17 for loading the boot file by another program proceeds smoothly.

  If the current read speed CVR has not fallen below the release speed threshold QRT at block 215, the current read speed CVR is sufficiently reduced because the boot file has been read by the previous queued process. Therefore, queuing is continued in block 217 and the process proceeds to block 203. If the current read speed CVR is less than the release speed threshold QRT in block 215, the process of the read request queued in block 219 is taken out from the queue using a first-in first-out (FIFO) method.

  In block 223, the boot I / O driver 107 performs a process of passing the read request process to the disk driver 71 to access the HDD 17. In block 225, when the boot completion check program 109 detects a boot completion state based on the CPU usage rate, a boot completion signal is sent to the I / O control service 101. In block 227, the I / O control service 101 boots. The delay processing of the I / O driver 107 is stopped and the subsequent read request process is passed to the disk driver 71 without queuing at all. The boot completion check program 109 records the boot completion time in the boot I / O log 105. Furthermore, the boot I / O driver 107 records the average reading speed AVR in the internal table 121, and also records information indicating that the queuing execution flag has been set to ON even once during the boot. .

  According to the delay processing of the control target program shown in FIG. 4, the time for the control target program to read the boot file into the dedicated area at the time of booting is long, and the time until the boot system code 51 loads the boot file is short. Become. The boot completion state can be defined as a state in which an application used by the user can be executed without any trouble after the boot starts. An environment in which the user can execute the application earlier than before can be realized by the delay processing for the control target program. When the program to be controlled is the AV program 53, the time for completing the virus check is delayed by the time that the process is queued, but the virus check is performed even when a new file is stored in the HDD 17, so the load is loaded. There is usually no problem if the virus check time for the boot file is delayed by that amount. In addition, the process queuing is different from the process stop, and the AV program 53 accesses the HDD with a slow response speed and determines that the process is normally processed by the system. Don't do that.

  Here, a method for generating a boot completion signal by the boot completion check program 109 will be described with reference to the flowchart of FIG. The boot completion time in this embodiment is defined as the elapsed time from when the boot completion check program 109 that is automatically started at the time of booting until the overall CPU usage rate continuously falls below a predetermined value for a predetermined time or more. To do. In the present embodiment, 10 seconds is set as the predetermined time, and 15% is set as the predetermined value.

  When the boot completion check program is started at a predetermined stage of boot in block 501, the OS Shell Startup 61 determines in block 503 whether the boot completion check program is registered in the registry. If it is not registered, it is registered in the OS Shell Startup 61 at block 505, and this time it ends without generating a boot completion signal and measuring the boot completion time at block 507. If the boot completion check program 109 is registered in the OS Shell Startup 61 in block 503, the variable COUNTDOWN is set in block 509, and the CPU usage rate is 15% or less by blocks 509, 511, 513, 515, and 517. It is determined whether or not the state continues for 10 seconds.

  When the CPU usage rate and duration conditions are satisfied at block 515, the boot completion check program 109 sends a boot completion signal to the I / O control service 101 at block 519 and sets the boot completion time to the boot I / O log 105. And block 521 ends. The boot completion time according to the above definition is not the time from when the computer 10 is turned on until the application can be started without any trouble. The application can be started without any trouble when the CPU usage rate becomes 15% or less, but in this embodiment, the threshold is changed and executed in order to obtain the optimum values of the start speed threshold QST and the release speed threshold QRT. The above definition is adopted because it is only necessary to know the difference in boot completion time for each boot.

[Optimum threshold determination process (overall)]
FIG. 5 to FIG. 7 are flowcharts showing processing procedures for determining the optimum values of the start speed threshold value QST and the release speed threshold value QRT for the control target program executed by the I / O control service 101. FIG. 5 shows the overall processing procedure, FIG. 6 shows the procedure for determining the optimum start speed threshold value QST, and FIG. 7 shows the procedure for determining the optimum release speed threshold value QRT. In FIG. 5, in block 301, the boot I / O driver 107 executes the procedure shown in FIG. When the current boot is completed in block 303, the internal table 121 of the boot I / O driver 107 includes the process name of the control target program or the candidate for the control target program at the end of the previous boot, the start speed threshold QST. The release speed QRT and the average reading speed AVR are recorded, and the boot completion time BCT is recorded in the boot I / O log 105.

  In block 305, the I / O control service 101 makes an inquiry to the boot I / O driver 107, and the control in which the queuing execution flag is turned on during the current boot recorded in the internal table 121 is controlled. The average reading speed AVR, start speed threshold value QST, and release speed QRT for the target program or control target program candidate process are acquired and recorded in the boot I / O log 105. In block 307, the optimum value of the start speed threshold value QST is determined. In block 309, it is determined whether the I / O control service 101 has determined the optimum value of the start speed threshold value QST in this boot. If it is determined that it cannot be determined, the process proceeds to block 311 and the determination of the optimum value is left to the next boot. When the I / O control service 101 determines in block 309 that the optimum value of the start speed threshold value QST has been determined, the process is identified as being generated by the control target program, and the process proceeds to block 313. A process for determining the optimum value of the release speed threshold QRT is performed. In block 315, it is determined whether or not the I / O control service 101 has determined the optimum value of the release speed threshold QRT in the current boot. If it is determined that it cannot be determined, the process proceeds to block 311 and the determination of the optimum value is left to the next boot. When it is determined in block 315 that the I / O control service 101 has determined the optimum value of the release speed threshold QRT, in block 317 all the optimum value determination processing ends. When the optimum threshold value is determined, queuing control based on the optimum threshold value is performed by the boot I / O driver 107 in the procedure of FIG.

[Optimum threshold determination process (QST)]
Next, a process for determining the optimum value of the start speed threshold value QST will be described with reference to FIG. The blocks 351 and 365 in FIG. 6 correspond to the blocks 307 and 311 in FIG. 5 respectively, and the transition from the block 359 to the block 371 in FIG. 6 corresponds to the transition from the block 309 to the block 313 in FIG. In this embodiment, the boot I / O driver 107 performs queuing based on the current reading speed CVR for a process in which the start speed threshold value QST and the release speed threshold value QRT are set without recognizing the control target program in advance. Start. The I / O control service 101 measures the boot completion time BCT and the average reading speed AVR for each boot to identify the control target program and determine the optimum start speed threshold value QST and release speed threshold value QRT. -It takes time to make a decision because the file needs to be booted multiple times.

  In order to determine the optimum threshold and identify the program to be controlled at an early stage, in block 353, the I / O control service 101 executes the boot several times and reads it to the dedicated area in all the boot files. A program in which the total number of bytes of the boot file exceeds a predetermined value is set as a control target program candidate. The boot I / O driver 107 measures the total number of bytes read. A boot file with a large number of bytes read at the time of booting is likely to cause delays in loading other boot files. Therefore, the I / O control service 101 controls the program by first setting it as a candidate for a control target program. It is possible to shorten the time required for specifying the target program and setting the optimum speed threshold. The user may set candidates for the control target program.

When the current boot is completed in block 355, the I / O control service 101 refers to the boot I / O log 105 in block 357, and determines whether the start speed threshold value QST is an optimal value in block 359. The boot I / O log 105 in FIG. 3 shows how the start speed threshold value QST changes from V ₀ as an initial value to V ₁ , V ₂ ... And an optimal value V _n at every boot. ing. The initial value V ₀ is held by the I / O control service 101. In the first to fourth boots, the release speed threshold QRT is set to a value that is smaller than the start speed threshold QST by a constant value β ₀ . The boot I / O log 105 records a boot completion time BCT and an average reading speed AVR when each boot is completed.

In the boot I / O log 105, the I / O control service 101 sets the start speed threshold value QST to the initial maximum value V ₀ in the first boot, and V ₁ = V ₀ − in the second boot. It is recorded that α ₀ is set and V ₂ = V ₁ −α ₁ is set in the third boot. When booting is repeated while the start speed threshold QST is lowered, the average read speed AVR of the boot file read by the control target program is lowered and the boot completion time BCT is shortened, but the start speed threshold QST is lowered. However, the boot completion time BCT does not change in the shortening direction beyond that due to the file transfer speed of the HDD 17.

The I / O control service 101 determines the optimum value of the start speed threshold value QST as a value V _n when the average reading speed AVR becomes maximum within a range where the boot completion time BCT does not change. The I / O control service 101 refers to the boot I / O log 105 in order to determine the optimum value of the start speed threshold value QST, and is initially relatively large from the start speed threshold value QST at the time of the current boot. The value obtained by subtracting the change α is set as the start speed threshold QST at the next boot. However, as the number of boots increases, the degree of shortening of the boot completion time BCT decreases, so the change α to be subtracted is reduced. To go. The I / O control service 101 sets the next start speed threshold QST by adding or subtracting the change α to the current start speed threshold QST while gradually reducing the change α. Optimal start speed threshold value V _n is determined.

  The procedure until the I / O control service 101 determines the optimum start speed threshold value QST is shown in blocks 357, 359, 361, 363, and 365 in FIG. In block 359, if the I / O control service 101 determines that the optimum start speed threshold value QST has not been determined, the process proceeds to block 360, where the start speed threshold value QST set in the current boot is changed and generated. It is determined whether or not the next boot start speed threshold QST is equal to or higher than the minimum value. The I / O control service 101 excludes the program that does not shorten the boot completion time even if the start speed threshold value QST is less than the minimum value from the control target program in block 364, and moves to block 365.

If the start speed threshold value QST set for the next boot in block 360 is greater than or equal to the minimum value, the start speed threshold value QST changed in block 361 is set in the registry of the boot I / O driver 107, and boot is executed in block 363. QRT = QST-β is set in the registry of the I / O driver 107. Here, the change amount β is a constant for providing a hysteresis between the start speed threshold value QST and the release speed threshold value QRT. In this embodiment, the I / O control service 101 sets the change amount β to a constant β ₀ until the start speed threshold value QST is determined. Then, the next boot is performed at block 365.

  When returning from the block 363 to the block 353 via the block 365, the I / O control service 101 sets the program as a control target program candidate until the optimum start speed threshold value QST is determined. When returning from the block 364 to the block 353 via the block 365, the I / O control service 101 sets other programs excluding the program as candidates for the control target program in the block 353.

  If the I / O control service 101 determines that the optimum start speed threshold value QST has been determined in block 359, the I / O control service 101 identifies the program as a control target program. In block 367, the optimum start speed threshold value QST is registered in the boot I / O database 103, and the optimization completion flag is set to ON. When the optimization completion flag is set in the I / O database, the I / O control service 101 always sets the optimum start speed threshold value QST in the registry of the boot I / O driver 107 for the process. Set. In block 369, the I / O control service 101 sets the optimum start speed threshold value QST in the registry of the boot I / O driver 107, and in block 371, the process for determining the start speed threshold value QST is ended.

[Optimum threshold determination processing (QRT)]
Next, a process for determining the optimum value of the release speed threshold QRT will be described with reference to FIG. The blocks 401 and 413 in FIG. 7 correspond to the blocks 313 and 311 in FIG. 5 respectively, and the transition from the block 407 to the block 419 in FIG. 7 corresponds to the transition from the block 315 to the block 317 in FIG. The release speed threshold value QRT is a threshold value for releasing queuing when the current reading speed CVR once exceeds the start speed threshold value QST and queuing of the process is started and then the current reading speed CVR decreases.

Therefore, the release speed threshold value QRT is always smaller than the start speed threshold value QST, and the queuing time becomes longer as the difference with respect to the start speed threshold value QST becomes larger. Optimal value of the release velocity threshold QRT likewise the optimum value of the start speed threshold QST, determined as the value S _n of time to maximize the average read speed AVR scope boot completion time BCT does not change. Upon completion of the current boot performed with the optimal start speed threshold value QST set in block 403, the I / O control service 101 refers to the boot I / O log 105 in block 405, and the release speed threshold value in block 407. It is determined whether QRT is an optimal value. The boot I / O log 105 in FIG. 3, the start speed threshold QST at the fourth boot is set to the optimum value V _n, the fourth boot from 7 th boot to the release velocity threshold QRT initial value for each boot shows a situation in which changing to _{S n} are _{S 1, S} 2 ··· and the optimum value from the _{S 0} as. The boot I / O log 105 records a boot completion time BCT and an average reading speed AVR for each boot. The release speed threshold QRT is set to a value obtained by subtracting the decrement β from the start speed threshold QST.

In block 405, the I / O control service 101 sets the decrement β to the optimum start speed threshold QST to be relatively small in the first boot after obtaining the optimum value of the start speed threshold QST, and gradually decreases the decrement β. While increasing, observe the boot completion time BCT. When the I / O control service 101 determines that the boot completion time BCT is not shortened any more, it determines that the optimum release speed threshold QRT has been determined. The procedure until the I / O control service 101 determines the optimum release speed threshold QRT is shown in blocks 407, 409, 411, and 413 in FIG. If the I / O control service 101 determines in block 407 that the optimum release speed threshold QRT has not been determined, the release speed threshold QRT decreased in block 409 is set in the registry of the boot I / O driver 107, and block In 411, V _n that is the optimum start speed threshold value QST is set in the registry of the boot I / O driver 107. Then, the next boot is performed at block 413.

  If the I / O control service 101 determines that the optimum release speed threshold QRT has been determined in block 407, the optimum release speed threshold QRT is registered in the boot I / O database 103 in block 415 and the optimum Set the initialization complete flag to on. The I / O control service 101 sets the optimum start speed threshold value QRT in the registry of the boot I / O driver 107 in block 419, and ends the determination process of the release speed threshold value QRT in block 419.

  Although the HDD has been described as an example of the boot disk so far, the boot disk may be a flash drive (SSD) or an optical disk drive (ODD). Further, the boot disk does not have to be a component of the computer 10, and may be connected to a computer on which the module of FIG. 2 is mounted through a network.

  4 to 7, the boot I / O driver 107 executes and cancels queuing based on the current reading speed CVR. In the present invention, it is also possible to determine whether to execute or cancel queuing using parameters other than the current reading speed CVR. For example, in the boot stage, when a lot of programs are loaded after a lapse of time since the computer 10 is started, they start reading other files, so that the transfer speed of the boot file to be loaded becomes slower. Therefore, at the initial stage of a certain boot, the boot file is loaded without queuing the control target program, and after the total amount of boot files read by the control target program reaches a certain amount, You can also queue program processes. In this case, the total number of bytes of the read boot file can be set as the threshold value for starting queuing, and the optimum value can be determined and queued in the same procedure as that shown in FIGS. Since queuing in this case is canceled by a boot completion signal, it is not necessary to set a threshold for canceling queuing.

  Although the present invention has been described with the specific embodiments shown in the drawings, the present invention is not limited to the embodiments shown in the drawings, and is known so far as long as the effects of the present invention are achieved. It goes without saying that any configuration can be adopted.

103 ... Boot I / O database 105 ... Boot I / O log 121 ... Internal table of the boot I / O driver 107

Claims (17)

In cooperation with the operating system on a computer with a boot medium storing a boot file,
Initiating loading of the boot file from the boot medium into an execution region of main memory;
A control target program starts reading the boot file from the boot medium to a dedicated area of the main memory; and
Measuring a reading speed at which the control target program reads the boot file;
A computer program for executing a process having a step of executing or canceling queuing of a process generated for reading of the boot file by the control target program during a boot period based on the reading speed.   The computer program according to claim 1, wherein the control target program is an antivirus program. Setting a start speed threshold that controls queuing of the process and a release speed threshold that is less than the start speed threshold;
Queuing the process when the read speed is greater than or equal to the start speed threshold;
The computer program according to claim 1, further comprising a step of releasing the queuing when the reading speed falls below the release speed threshold.   The computer program according to claim 3, further comprising the step of changing the start speed threshold value at the next boot for each boot, measuring a boot completion time, and determining an optimum start speed threshold value.   The computer program according to claim 4, wherein the step of determining the optimum start speed threshold includes a step of measuring an average read speed with respect to a total amount of the boot file read by the control target program until the boot is completed. The computer program according to claim 5, wherein the optimum start speed threshold is a value when the average reading speed reaches a maximum in a range where the boot completion time does not change .   The computer method according to any one of claims 4 to 6, wherein the step of determining the optimum start speed threshold includes decreasing the start speed threshold for each boot until the optimum start speed threshold is determined. program.   The computer program according to any one of claims 3 to 7, further comprising a step of determining an optimum release speed threshold value by measuring the boot completion time by changing the release speed threshold value at the next boot for each boot. 9. The step of determining the optimum start speed threshold includes selecting a program in which the total amount of boot files read into the dedicated area exceeds a predetermined value in the boot file. A computer program according to any one of the above.   The computer program according to any one of claims 3 to 9, wherein normal processing that does not queue the process when the start speed threshold is not set is performed. In cooperation with an operating system on a computer having a boot medium storing a boot file containing a control target program,
Initiating loading of the boot file from the boot medium into an execution region of main memory;
The control target program starts reading the boot file from the boot medium to a dedicated area of the main memory; and
Measuring the total amount of the boot file read from the boot medium by the control target program;
Setting a total amount threshold value for controlling queuing of a process generated by the control target program for reading the boot file;
And queuing the process when the measured total amount of boot files is equal to or greater than the total amount threshold. A computer capable of booting from a boot disk containing a boot file,
Main memory with an execution area and a dedicated area;
Boot system code for causing the computer to implement a function to start loading the boot file from the boot disk to the execution region;
Speed measuring means for measuring a reading speed at which the control target program reads the boot file from the boot disk to the dedicated area;
A computer having control means for executing or canceling queuing of a process generated by the control target program for reading the boot file during a boot period based on the reading speed. The computer according to claim 12, wherein the control target program causes the computer to realize a function of issuing a warning when execution of a process generated for reading the boot file is stopped.   14. The computer according to claim 12, further comprising: a service program that realizes a function of setting a speed threshold for execution and cancellation of the queuing to the control unit. The service program the computer to realize the function of determining the optimum value of the speed threshold the speed threshold at next boot which is determined based on the boot completion time measured for each boot is set to the control means The computer according to claim 14. The service program is further said computer, according to claim to realize the function of the control target program determines the speed threshold at next boot based on the average read rate with respect to the total amount of the boot file read by the boot completion 15. The computer according to 15. A computer capable of booting from a boot disk containing a boot file,
Main memory with an execution area and a dedicated area;
Boot system code for causing the computer to implement a function to start loading the boot file from the boot disk to the execution region;
A total amount measuring means for measuring a total amount of the boot file read by the control target program from the boot disk to the dedicated area;
A computer having control means for queuing a process generated by the control target program for reading the boot file during a boot period based on the measured total amount of the boot file;

Images