Some programs in the process of running, will frequently request and release memory, such as Oracle's Listener connector using the dedicated settings, and the connection is a short connection, will continue to establish new connections, request memory space, complete the client SQL request, and then free memory, exit. When the system is busy, the idea is that the system builds many new processes, the process numbers change, there are a lot of Sr and Fr, and FR is almost equal to SR (in the case of a lot of system memory, FR is usually only 1/6-1/4sr size, or even less). This means that 4-6 blocks of physical memory have been retrieved before a piece of memory can be released. In this case, even if the system has enough memory for scheduling, it will cause the system to run slowly because the system wastes a lot of CPU resources for memory data retrieval. The workaround is to turn the short connection type into a long connection through Oracle settings, such as setting shared Server/service, lengthening the idle wait time of the connector, and even changing the way the client works, avoiding unnecessary memory scans/requests and release actions.