Windows Terminal Server Tuning for BESConsole use

(imported topic written by MrFixit)

I know many use Terminal Servers for the BESConsole. We have been observing that non paged and paged pools indicate that some leaking is going on. Below is top of a poolmon snapshot of a TS that is dedicated to BESconsole usage that has been up for a while with steady use.

Note: Servers are Windows 2003 x64 SP2 and this same pattern shows up on all my TS where we run the BESConsole. Also I’m still on 7.2.5.22.

Tag Type Allocs Frees Diff Bytes Per Alloc

MmSt Paged 71501441 70983233 518208 1079870352 2083

Ntff Paged 49994499 49504778 489721 548487520 1120

IoNm Paged -950333782 -950822666 488884 148572416 303

File Nonp -1492358059 -1492871806 513747 140445056 273

Ntfr Nonp 13977079 12966701 1010378 129330320 128

CcVa Nonp 1 0 1 94375936 94375936

Questions are?

Have you seen this as well? If so what have you done to reduce the consumption or eliminate it?

Has anyone overridden the memory Management trimming process? Did it help? What values did you end up using?

thanks,

-Gary