High memory usage mapped file Windows Server 2012

Question

Greeting,

Currently I am running an IIS server to serve applications , but currently I am having some trouble with the memory usage.

As you can see, Mapped File is using a lot of memory on standby, but I am not sure what application or process that causes this.
Here are some more pictures of detailed process that are currently running on my server

Do you guys have any idea what could cause this high memory usage? I really appreciate any help.

Thank you

Syehino

Answer 1

Hi @Syed Nazirul ,

You can read this docs to know file mapping. But I think it cannot provide any useful information about high memory.

I researched high memory of first w3wp.exe. A healthy IIS Server will consume approximately 300 - 600 MB, maybe 700 MB RAM when busy. The w3wp.exe's memory is 772MB. Though it is more than 700MB, it still looks normal.

Maybe you have a lot of concurrent web users. Maybe the resources loaded on the web console are intensive.......All these possibilities will cause IIS busy. You can set regular time interval of application pool to reduce memory.

Then I also researched shell32.dll, system.evtx and winscp.exe. Those of them have high standby and that is abnormal. But they are files refered by system, should not have high usage. If your server can be turn off or restart for a while, please restart it to check whether these file still have high usage.

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our  documentation  to enable e-mail notifications if you want to receive the related email notification for this thread.

Best regards,
Bruce Zhang

Answer 2

You misunderstand what mapped files are. They are an operating system feature where an application opens a file as mapped. Then instead of using file read/write, the file is mapped to memory like a page file, and the application uses memory access operations and is generally faster than using the file system.

The mapped file will have a working set of how many of its pages will be in real memory.