{"id":362495,"date":"2024-05-21T01:36:15","date_gmt":"2024-05-21T01:36:15","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=362495"},"modified":"-0001-11-30T00:00:00","modified_gmt":"2024-05-21T01:36:15","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=362495","title":{"rendered":"Memory consumption of .NET applications on Linux<\/span>"},"content":{"rendered":"
<\/div>\n
\n
\n
\n
\n

Introduction<\/h2>\n

In this article, I will cover the memory consumption of .NET applications on Linux. Firstly, we will try to understand the idea of virtual memory. Then, we will examine the memory statistics that Linux provides, such as RSS (Resident Set Size), VmData, RES (Resident Memory Size), and SWAP. Following that, we will delve into specifics related to the .NET.<\/p>\n

Basic memory stats in Linux<\/h2>\n

Let\u2019s create a basic ASP.NET application from the default template, publish it in framework-dependent mode and run it on Linux.<\/p>\n

I\u2019ve started the application on Linux and executed the top command.<\/p>\n

<\/figure>\n

We have three memory-related statistics here: 262Gb, 66Mb and 57Mb, but how do we find the \u201ctrue\u201d memory consumption? Unfortunately, it\u2019s impossible unless we understand the idea of virtual memory and the principles of memory allocation.<\/p>\n

Virtual memory<\/h2>\n

In older operation systems and on devices like Arduino, you have direct access to physical memory. It means that operations like mov 0, 42 would actually load \u201c42\u201d to the very beginning of the CPU\u2019s physical memory. But modern OSs like Linux and Windows, with help from CPU don\u2019t give you access to physical memory. A mechanism called virtualisation is used instead.<\/p>\n

Let\u2019s say we have two processes which load some files from the disk and allocate some memory to store data.<\/p>\n

Each of the processes has so-called virtual memory. Only virtual memory can be accessed inside the process. When you try to put 42 to a memory address like 7f849c021000 it doesn\u2019t mean that this very address of the physical memory will be accessed. Moreover, it doesn\u2019t mean any physical storage is allocated before you access it.<\/p>\n

<\/figure>\n

Let\u2019s look at the diagram showing two processes and go through all the memory segments these processes have in the virtual memory space.<\/p>\n

First process<\/h4>\n