Shulou(Shulou.com)05/31 Report--

How can the server allocate the memory in the system page buffer pool? aiming at this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

Symptom information:

When the server is heavily loaded, the server service may repeatedly record the following error in the system event log, indicating that the server's page buffer pool is out of memory:

Source-SRV

Type-error

Event ID-2020

Description-

The server cannot be allocated through the system page share area because the share area is currently empty.

Data-

0000: 00040000 00540001 00000000 c00007e4

0010: 00000000 c000009a 00000000 00000000

0020: 00000000 00000000 0000000b

The cause of the problem:

There are several factors that can deplete the supply of page buffer pool memory. Enabling pool marking and taking pool snapshots at different intervals can help you understand which driver is using page buffer pool memory. If the pool snapshot indicates that the MmSt tag (Mm area object prototype PTE) uses the most pool memory, and the page buffer pool memory is exhausted, or if the system is logging error event 2020, it is most likely because there are a large number of files open on the server. By default, when the system reaches 80% of the total page buffer pool size, the memory manager tries to trim the allocated page buffer pool memory. Depending on the system configuration, the maximum possible page buffer pool memory on the computer can be 343MB, and 80% of this amount is 274MB. If the memory manager fails to keep up with the demand, the events listed in the symptoms section of this article may occur. By optimizing the memory manager to start the trimming process at an earlier time (for example, when the memory of the page buffer pool used reaches 60%), the demand of the page buffer pool can be met during the sudden peak use. in order to avoid insufficient memory in the page buffer pool.

Solution:

Warning: if you modify the registry incorrectly using Registry Editor or other methods, it can cause serious problems. These problems may need to be resolved by reinstalling the operating system. Microsoft does not guarantee that you can solve these problems. Modifying the registry is at your own risk.

The following optimization recommendations are helpful in alleviating this problem:

Start the Registry Editor (Regedt32.exe).

Locate and click the following registry key in the registry:

HKEY_LOCAL_MACHINE\ System\ CurrentControlSet\ Control\ Session Manager\ Memory Management

On the Edit menu, click add numeric values, and then add the following registry values:

Numeric name: PoolUsageMaximum

Data type: REG_DWORD

Base: decimal

Numerical data: 60

Setting this value to 60 tells the memory manager to start the trimming process when it reaches 60% of PagedPoolMax instead of the default setting of 80%. If the 60% threshold is not enough to handle peaks in activity, reduce this setting to 50% or 40%.

Numeric name: PagedPoolSize

Data type: REG_DWORD

Base: hexadecimal

Numeric data: 0xFFFFFFFF

Setting PagedPoolSize to 0xFFFFFFFF allocates the largest page buffer pool to the computer to replace other resources.

Exit Registry Editor.

Restart the server for the changes to take effect.

The answer to the question about how the server cannot allocate the memory in the system page buffer pool is shared here. I hope the above content can be of some help to you, if you still have a lot of doubts to be solved. You can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.