Memory handling on large-file-copy jobs


When I start copying large files (>2GB) from one Windows 2008 Server to another both servers consume the whole physical memory for file caching.
When the copy job starts it seems that Windows uses mostly all memory for file-copy caching.

Is there any known way to prevent a windows server 2008 to decrease the amount of memory used for file service caching ?

Thanks for answers,
Mario

.

Relevant Pages

  • [NT] NNTP Service in Windows Contains Memory Leak
    ... NNTP Service in Windows Contains Memory Leak ... An affected server could be restored to normal service by ...
    (Securiteam)
  • Re: Windows 2000 Server StandardEdition /PAE Question
    ... specifically the SQL Server 2000 Standard Edition on that server. ... His point is that applications can only use up to 2 GB or RAM on ... a process running under Windows 2000 or Windows Server 2003 can ... used) with some of the memory being physical memory and some being virtual ...
    (microsoft.public.win2000.general)
  • Re: W23K-Terminalserver mit Qber_8GB_RAM_?=
    ... schreibst und somit auch bei Windows 2003 Enterprise Edition nur max. ... Wesentlich sinnvoller wären zwei kleinere Server gewesen, ... Jede Applikation bekommt seine eigenen 2 GB User Memory Space. ... Die anderen 2 GB Kernel Memory Space sind zwischen allen ...
    (microsoft.public.de.german.windows.terminaldienste)
  • Re: ASP.NET User.Identity.Name value after a domain username chang
    ... Since .NET is just calling into Windows API calls to resolve the user name, ... I have an ASP.NET application that is on a Win2000 server in a domain ... I have a very confusing issue when the domain login of a user is ... I thought this might have been some caching issue on the client so I ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: ASP .NET poor performance. Memory going unused??
    ... 1315 context switches per second is a lot, especially on Windows 2003 server ... objects, again, effectively serializing your requests. ... create a lot of data in the memory the memory usage should be fairly static. ...
    (microsoft.public.dotnet.framework.performance)