A memory management method and system adopting analysis-feedback-tuning mode

Abstract

The invention relates to a memory management method adopting an analysis-feedback-tuning mode. The method comprises the following steps: step one: setting a kernel parameter of a configurable efficient memory pool in a configuration file, linking the configuration file to third-party application software; step two: running the third-party application software; step three: obtaining a memory usage analysis result in the running period after the running is finished; step four: judging whether a memory usage rate is an optimal value;; if the memory usage rate is not the optimal value, adjusting the kernel parameter according to the feedback of the analysis result, and repeating the step two to four; if the memory usage rate is the optimal value, regarding the kernel parameter as the optimal kernel parameter, and finishing the procedure. The invention further provides a memory management system for realizing the method. By use of the method disclosed by the invention, the problems of memory fragmentation, seriously reduced performance, and absent protection mechanism in the distributed memory are solved.

Description

technical field [0001] The invention belongs to the field of computer memory management, and specifically relates to a memory management method and system adopting an analysis-feedback-tuning mode, and is mainly used for optimizing, troubleshooting and testing memory usage. Background technique [0002] In computer memory management, the C / C++ standard heap management algorithm is mainly used, but this algorithm has two main defects: [0003] 1. For a large amount of memory allocation and recovery efficiency is not high, resulting in memory fragmentation, performance degradation. [0004] The basic principle of the general memory management algorithm provided by the operating system is to divide the complete heap memory into memory blocks of different sizes, and use a linked list structure to link these memory blocks of different sizes together. When allocating memory, you first need to search for a memory block of a suitable size. If there is no memory block of a suitable ...

AI Technical Summary

Problems solved by technology

Running such software for a long time will cause a lot of memory fragmentation

Since such memory fragments in the memory management algorithm of the C++ / C standard library are also organized together in chains, it will greatly increase the time for subsequent memory allocation

Moreover, these memory fragments are not continuous, which makes it impossible to continue to allocate larger-sized memory, but in fact, the system still has enough free memory at this time

[0006] 2. There is no protection mechanism for the use of allocated memory, and there are no protection measures for common problems such as memory write out of bounds, illegal access, and memory leaks

Any allocation / freeing inconsistencies can lead to memory leaks or system crashes

Moreover, the problems caused by memory writing out of bounds and illegal access are very difficult to locate and solve, so it will increase the burden on programmers and require programmers to have a high level of system knowledge

Usually memory corruption is caused by out-of-bounds writes to arrays or pointers

For example, the array writes out of bounds, and 110 bytes are continuously written to a temporarily allocated 100-byte array. At this time, the last 10 bytes are destroyed, and these 10 bytes are the header structure of another data block. , causing the system to crash when another data block is freed

Writing out of bounds for pointers can cause more serious problems, sometimes out of bounds writing to pointers can randomly destroy some data structures without causing the system to crash immediately

But as the software continues to run, it will cause a series of subsequent memory corruptions, eventually leading to software data errors or system crashes

By this time, it is impossible to track down the most original damage point, and it is impossible to find the problem. This is an extremely difficult problem in C / C++ development, and it usually takes programmers a lot of time to try to solve it, resulting in the entire Project development delays

If such problems occur in the secondary development and maintenance process in the later stage, it is very likely that the problem cannot be found and solved, and eventually the entire software life cycle will be shortened.

[0008] In short, in the memory management algorithm of the C++ / C standard library, the efficiency of a large amount of memory allocation and recovery is not high, and the performance is very unstable.

There is no protection mechanism for allocated memory, and there is no protection for common problems such as memory corruption and memory leaks

Images