大网数据广告活动
Web服务器与PHP

Worker Process takes much memory

· 52CE 我爱测

This article provides resolutions for the problem that Worker Process may allocate a large amount of memory when you have a complex directory structure on IIS.

This article provides resolutions for the problem where Worker Process may allocate large amounts of memory when you have a complex content directory structure on Microsoft Internet Information Services (IIS).

Original product version:   Windows Server 2008, 2008 R2, 2012, 2012 R2
Original KB number:   3020858

Symptoms

Consider the following scenario:

  • You install the Web Server role from IIS.
  • You have a content directory whose structure is complex. For example, you have a deep tree that includes many child directories in a parent directory.
  • Users send requests for many unique URLs. For example, users send requests for many virtual directories or applications.

In this scenario, the worker process may suddenly allocate a large amount of memory.

Cause

IIS caches configuration information by using a virtual directory path. Additionally, a hash table to access the configuration information efficiently is created. If many unique URLs are accessed, and if the size of the hash table becomes insufficient, the hash table is extended. If you also have a complex directory structure, the size of the hash table may be extended greatly.

Workaround

To work around this issue, use one of the following methods:

  • Simplify the content directory structure.
  • Increase the frequency of recycling the worker process.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 04/07/2020
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。