What if the server cannot allocate it through the system's non-page sharing area?

The server can not be allocated through the system non-page sharing area. For this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more small partners who want to solve this problem find a simpler and easier way.

Details: The server could not allocate the pool from the system because the pool is empty. In addition, in the Poolmon log file you find that the NTID Pooltag is exhausting high non-paged pool memory.

By optimizing the memory manager so that it starts the trimming process earlier (e.g., when it reaches 40%), you can meet the page buffer pool requirements during bursts of peak usage and avoid page buffer pool memory.

Deficiencies.

The following optimization suggestions are helpful in mitigating this problem:

1. start a Registry Editor

(Regedt32.exe)。

2. Locate and click the following registry key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session

Manager\Memory Management

3. On the Edit menu, click Add Value, and then add the following registry value:

Value Name: PoolUsageMaximum

Data Type: REG_DWORD

Base: decimal

Data: 40

Setting this value to 40 informs the memory manager that it will not be able to reach 40% of PagedPoolMax before it reaches 40% instead of the default

Start the trimming process at 80%.

Value Name: PagedPoolSize

Data Type: REG_DWORD

Base: hexadecimal

Numerical data: 0xFFFFFF

Set PagedPoolSize to 0xFFFFFF (-1) to allocate the largest page buffer pool for the computer

to replace other resources.

4. Exit Registry Editor.

About the server can not be allocated through the system non-page sharing area to do the answer to the question shared here, I hope the above content can be of some help to everyone, if you still have a lot of doubts not solved, you can pay attention to the industry information channel to learn more related knowledge.