Es gibt dazu eine Technote:
Domino 6.x Running on Windows 2003 Takes Hours to Shut Down and Experiences Periodic Slowdowns
Technote (FAQ)
Problem
When shutting down a Domino server on Windows 2003, it has been found that the shutdown process releases memory very slowly, approximately 1MB per second per Domino task. For example, a process with 1GB of memory takes over 15 minutes to shut down, which can result in significant shutdown time because the release of each Domino task occurs sequentially, not in parallel.
Additionally, as Domino server tasks (e.g., Compact, Updall) load and unload on Windows 2003, the Domino server becomes unresponsive or sluggish for a period of time, depending on how much memory was allocated to that task. Customers have reported periods of slowdowns ranging from 1 to 15 minutes.
The slow release of memory for Domino processes can be viewed by examination of the Notes/Domino tasks in Windows Task Manager. Running NSD during slow shutdown does not produce any diagnostic data.
Solution
Microsoft Support has verified this is a Windows 2003 performance issue related to the function call UnMapViewOfFile. IBM Lotus Support and Development are working with Microsoft to resolve the issue. This same issue impacted Windows XP SP1 and is described under Microsoft Article #815227. Microsoft has indicated that the issue is addressed in the upcoming Windows 2003 SP1, currently in beta. Tests by IBM of Windows 2003 SP1 Beta are positive and show that the issue no longer occurs. For the latest estimate on when Windows 2003 SP1 will ship, please go to:
http://www.microsoft.com/windows/lifecycle/servicepacks.mspxAs a workaround, some customers have had success using the following Notes.ini parameter on the server, to limit memory usage:
ConstrainedSHMSizeMB=<x>
where x=the number of megabytes of shared memory to which Domino is constrained. ConstrainedSHMSizeMB=700 worked for one customer on a machine with 4GB of RAM.
Supporting Information:
Why is Domino and only a few other software products affected by this? Domino is using an API call that tells the Server OS to begin de-allocating memory for a task at the point it no long needs the memory. This is done to speed up the release of the memory and is considered good software coding. Eventually the OS would de-allocate this memory when it does its normal housekeeping. Unfortunately in this case, this exposes the issue in the Microsoft server OS.
