Unsatisfactory windows systems, slow, and poor performance

I remember that in the past Win98, the system was always reinstalled every month when the machine crashed. Later, Win2k came out, and the system was installed every six months to one year. Later, it became easier to have a ghost.

Later, Win2k Win 2003 WINXP was used to find that the performance was sometimes very slow, and it was a very slow thing.

View in Windows Task Manager --> select virtual memory, thread count, handle, user object count, and GDI in the selected column.

The first reason is that the entire system gets stuck when the hard disk reads and writes large files. Why? I don't know if Windows 7 can solve this problem! Generally, reading and writing large files, such as 4G movies, takes a long time.

At this time, users generally chat via QQ and read some web pages. These operations are purely memory operations, maybe a small number of I/O operations, but they are very stuck. The interface is broken, and the response is slow. It is very uncomfortable!

In terms of management of the second virtual memory, the virtual memory occupied by the process is released only when the process is completely exited. for example, after browsing 100 webpages with firfox, the memory occupied 200 MB, and the virtual memory occupied MB. you can only minimize the actual memory, but the virtual memory is not released. it may be the release of free, delete, and so on in the program. the operating system does not release the virtual memory.

When there are many processes in the Windows Task Manager, this virtual memory occupies a lot of space, leading to a very poor system performance.

Third, when a process is very busy and occupies 100% of the CPU time, the system will be very stuck. if the process is endless, You have to restart the computer, and the data of other applications that you have enabled at the same time cannot be saved.

For example, anti-virus software

The fourth advantage was the use of office2007's excle 2007, which found that it would not take long before it occupied up to 99999 of the GDI objects, making the interface of other applications dull.

The fifth Sharing Problem Windows itself provides many things for other applications to share and use. however, many applications can overwrite your own DLL and copy it to the system directory. this may cause problems such as security, stability, and performance.

I suggest the following modifications for the above five points:

1. When the user does not activate the interface of the Program on the desktop, the virtual memory occupied by the application is released internally or the proportion of the virtual memory will be released when it reaches a certain ratio.

2 Io problems when copying large files, read/write Io processes occupy 80% of the IO capability, and 20% of the capability is empty for temporary use by other programs. at the same time, it does not occupy too much CPU seek time. that is to say, the 40% CPU time is used to respond to users by other applications.

3. The maximum CPU usage is 80% by default. You can set the CPU usage of each program.

4. Set the number of threads, GDI objects, and user objects for each application. Do not fill the maximum capacity of the system.

5. Windows is installed in a single partition. This partition can only be read and cannot be written. To write data, you can start it in F8 mode.