SAP Knowledge Base Article - Preview

2488097 - FAQ: Memory usage for the ABAP Server on Windows


  1. What is the root cause for a high physical memory consumption shown in Windows Task Manager for a disp+work.exe process, while in  transaction SM50, the work process is in "Waiting" state?

  2. How is it possible to detect a memory leak of a process?

  3. How to configure memory when two or more SAP instances are installed on a Windows host?

  4. What are the possible root causes for a memory dump with error message "TSV_TNEW_PAGE_ALLOC_FAILED"?

  5. Is it still recommended to set Windows page file = 3 to 4 times of the main memory (RAM) size?

  6. Why my Virtual Machine (VM)  has few virtual memory  available  if  enough  virtual memory (RAM + pagefile) is configured in the server? 

   7.   Is it possible to  configure the SAP system with no  pagefile ?





Windows Server 2008 or higher



SAP NetWeaver all versions


virtual memory, commit, pagefile, paging, leak, high memory consumption,  high memory usage, RAM, PXA_NO_SHARED_MEMORY, TSV_TNEW_PAGE_ALLOC_FAILED   , KBA , BC-OP-NT , Windows , BC-INS-NT , SAP Netweaver based Solutions on Windows , BC-CST-MM , Memory Management , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.