![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi I have a C# app which opens a process and reads the output via a streamreader - the program reads the output from netstat. The amount of PF Delta goes up to 400 + ... I am concerned about this, however I do not have a memory leak, Page file is static and memory usage is also static. I would appreciate any pointers. .... |
#3
| |||
| |||
|
|
"James Jenkins" <james (@) tamarsolutions.co.uk> wrote in message news:Oj$Ffq0%23FHA.1988 (AT) TK2MSFTNGP12 (DOT) phx.gbl... Hi I have a C# app which opens a process and reads the output via a streamreader - the program reads the output from netstat. The amount of PF Delta goes up to 400 + ... I am concerned about this, however I do not have a memory leak, Page file is static and memory usage is also static. I would appreciate any pointers. ... Hi, I would not be concerned if performance is OK to you. Page faulting is not usually bad. It is controlled by the operating system itself. For example, when executable is started, OS might not load whole image in memory, but rather only load start page. Page fault handler will provide additional pages when needed (whole executable does not need to be loaded). Also, when you allocate memory, only address space is reserved. When data is written, page is allocated by the OS ("soft" page fault is generated). Bottom line is that memory model in windows is rather complex and if you don't see performance problems, don't bother. Regards, Goran |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |