When installing NSL on a Citrix server, what is the difference between aggressive and normal mode under the Citrix Server Memory Timing?

When installing NSL on a Citrix server, what is the difference between aggressive and normal mode under the Citrix Server Memory Timing?

Aggressive and normal mode sets the MinimizeActiveFootprint registry setting to the appropriate value as per the information below:

For each executable, Windows reserves memory for its execution. The amount or memory windows reserves for a program is not necessarily the amount that program requires, it is a best guess at how much it will use in the short term. This best guess is always a generous estimate.

The SecureLogin MinimizeActiveFootprint setting advises windows to trim the amount of reserved memory down to just the amount the program is actually using.  The setting can be used to advise windows to manage memory in the following ways:

• Continue guessing how much memory each of our executables needs, just like it does for every other program (This is the default mode)
• Continuously trim the amount of reserved memory down to only that which is currently being used. (This is aggressive mode)
• Aggressive mode can be used to minimize the memory footprint of a running program.

Additionally, there are some things the setting does NOT do;

• It does not start blocking DLLs
• It does not allow you to exclude SL components individually
• It does not modify the way the product runs
• It does not prevent SSO (or any other application) from running, regardless of what it is set to

The following registry settings further explain the setting;

[HKEY_CURRENT_USER/SOFTWARE/Protocom/SecureLogin] or [HKEY_LOCAL_MACHINE/SOFTWARE/Protocom/SecureLogin]

• MinimizeActiveFootprint - DWORD

This value is used during calls to the function

SetProcessWorkingSetSize.

• 0xFFFFFFFF / -1 - Routinely empties the work set for all SSO processes – Normal Mode (Default on Citrix)
• 0 - Does not call SetProcessWorkingSetSize - Default
• >0 - Uses SetProcessWorkingSetSize in an attempt to optimize the working set size for each SSO process – Aggressive Mode

For more information on SetProcessWorkingSetSize; http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/setprocessworkingsetsize.asp