Thread for high-performance computer NUMA perception and memory resource optimizing method and system

Abstract

The invention discloses a thread for high-performance computer NUMA perception and a memory resource optimizing method and system. The system comprises a runtime environment detection module used for detecting hardware resources and the number of parallel processes of a calculation node, a calculation resource distribution and management module used for distributing calculation resources for parallel processes and building the mapping between the parallel processes and the thread and a processor core and physical memory, a parallel programming interface, and a thread binding module which is used for providing the parallel programming interface, obtaining a binding position mask of the thread according to mapping relations and binding the executing thread to a corresponding CPU core. The invention further discloses a multi-thread memory manager for NUMA perception and a multi-thread memory management method of the multi-thread memory manager. The manager comprises a DSM memory management module and an SMP module memory pool which manage SMP modules which the MPI processes belong to and memory distributing and releasing in the single SMP module respectively, the system calling frequency of the memory operation can be reduced, the memory management performance is improved, remote site memory access behaviors of application programs are reduced, and the performance of the application programs is improved.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular to a high-performance computer NUMA (Non-Uniform Memory Access, non-uniform memory access)-aware thread and memory resource optimization method and system. Background technique [0002] At present, most mainstream high-performance computer nodes adopt DSM (Distributed Shared Memory, distributed shared storage structure) design. Such as figure 1 As shown, based on the computing node designed by the DSM architecture, each CPU (Center Process unit, central processing unit, and processor) can access its own memory module (local memory) through the memory controller in the CPU, or Access memory modules of other CPUs (remote memory) through high-speed Internet. The cost of accessing remote memory is higher than that of local memory, and even several times higher on some systems. This memory access feature is called NUMA (Non-Uniform Memory Access, non-uniform memory access). ...

AI Technical Summary

Problems solved by technology

[0004] 1. The operating system cannot perceive the memory access locality requirements of the application

[0005] The scheduling of threads by the operating system does not take into account the memory locality requirements of the application, and may schedule the execution thread to a processor core that is not adjacent to its memory, which may lead to remote memory access, thereby reducing the application program performance

[0006] 2. Application programming model memory management cannot be NUMA-aware

[0009] (1) The overhead of page migration is large and has a lag

[0010] (2) First-Touch memory allocation strategy and Auto-Migration automatic page migration technology cannot accurately predict the memory access behavior of the program, which may lead to inappropriate memory migration and remote memory access of the application

For numerical simulation programs, the memory access requirements are based on a variable size block (a piece of continuous memory requested by the application) as the basic unit. These memory blocks can range from several Bytes to several MBs. The smallest management unit of the LibNUMA library is a memory page. In many cases, the size of a memory page can contain many memory blocks. If the application frequently applies for fine-grained memory, it will cause a huge waste of memory resources.

[0013] (2) Frequent calls will lead to context switching between user mode and kernel mode, resulting in high overhead

The main functions of LibNUMA are implemented in the kernel mode. If the application directly and frequently calls the LibNUMA interface, it will cause too frequent context switching and greatly reduce the execution performance of the application.

Images