The system's virtual memory management mechanism and cache management mechanism provide support for this aspect. If the adjacent data happens to be the data that needs to be accessed immediately, then trigger I/O can be reduced. When a page fault interrupt causes disk I/O, generally not only the required page of data is taken, but adjacent data are read into physical memory. The minimum unit of I/O of the operating system is a page of 4KB. Support for the principle of spatial locality Because it knows in advance all the disk locations that need to be read in the future, it can be read in order as much as possible, reducing I/O times and saving Seek time when reading data.Ģ. When the program is started next time, the system will first load the data required for program startup into the memory. For example, it is easy to find "CHROME" on my " file.
This information will be recorded under\\Windows\Prefetch. Whenever a hard page interruption occurs when the application starts, the operating system will record the files accessed by the application and their locations. Reducing the number of times the program is read from the disk during the running process is to reduce the page fault (page fault) error, so that most of the data during the running process is loaded into the physical memory in advance, so there is a word called "read-ahead".ġ. If you can reduce the number of times to read the disk during the running of the program, you can Effectively increase speed. In today's faster and faster computing speed, the performance bottleneck is often I/O (SSD hard disk machines are obviously much faster than mechanical hard disks).
The startup speed is a very important point, how to speed it up? There is a simple principle: the principle of locality.
0 kommentar(er)
