[THIN] Re: Citrix Server Resources Exhausted
- From: "Jeremy Saunders" <jeremy@xxxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Thu, 31 May 2012 17:50:49 +0800
Yep, the irony is that unless you make changes the server dynamically sets
up these system memory allocations at startup. So if you have a 64GB server,
it's memory allocation in the 2GB kernel memory space will be different to
that of a 16GB server. Therefore you think you're on the right track by
pumping more memory in, but what you've actually done is handicap it..if you
know what I mean.
So if you do no memory tuning at all, you may find you get equal or better
performance from a 16GB server than a 32GB server.
In my opinion the sweet spot for a 32-bit Windows 2003 Enterprise Edition
Citrix server is 24GB.
This is only relevant in the Windows 32-bit world.
Cheers,
Jeremy.
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Dogers
Sent: Thursday, 31 May 2012 3:34 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Citrix Server Resources Exhausted
Ooh, now that's interesting! There's been some argument here as to what the
default pool limit is and I guess that solves it (I win!) :)
We've tried setting it to max, but that was on a 64G server which just went
into a boot up BSOD loop. Until this week, it was the only server that was
dying, but now some 16G servers are doing it, so we'll definitely give this
a go.
Thanks,
Andrew
On 30 May 2012 18:18, Jeremy Saunders <jeremy@xxxxxxxxxxxxxxxxxxxx> wrote:
Hi Andrew,
Have you played with the PoolUsageMaximum and PagedPoolSize values?
http://support.microsoft.com/kb/935649
Here's some info from my adm template you can use and play with the values:
--------------------------------------------------------------------------
CLASS MACHINE
CATEGORY "MACHINE Custom Settings"
POLICY "Memory Manager Tuning"
EXPLAIN !!MemoryManagerTuningExplain
KEYNAME
"SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management"
PART "PagedPoolSize" DROPDOWNLIST
VALUENAME "PagedPoolSize"
ITEMLIST
NAME
"Maximum - 0xFFFFFFFF" VALUE NUMERIC 4294967295 Default
NAME "650MB
- 0x28a00000" VALUE NUMERIC 681574400
NAME "450MB
- 0x1c200000" VALUE NUMERIC 471859200
NAME
"Default" VALUE NUMERIC 0
END ITEMLIST
END PART
PART "Setting PagedPoolSize to 0xFFFFFFFF
allocates the maximum paged" TEXT
END PART
PART "pool in lieu of other resources to the
computer." TEXT
END PART
PART "" TEXT
END PART
PART "PoolUsageMaximum" DROPDOWNLIST
VALUENAME "PoolUsageMaximum"
ITEMLIST
NAME "90"
VALUE NUMERIC 90
NAME "80"
VALUE NUMERIC 80
NAME "60"
VALUE NUMERIC 60 Default
NAME "50"
VALUE NUMERIC 50
NAME "40"
VALUE NUMERIC 40
NAME
"Delete" VALUE DELETE
END ITEMLIST
END PART
PART "Note that 60 Decimal instructs the
Memory Manager to trim allocated" TEXT
END PART
PART "paged pool memory when the system
reaches 60 percent of the total" TEXT
END PART
PART "paged pool. If a threshold of 60
percent is not enough to handle" TEXT
END PART
PART "spikes in activity, reduce this
setting to 50 percent or 40 percent." TEXT
END PART
END POLICY
END CATEGORY
[strings]
MemoryManagerTuningExplain="As per Microsoft TechNet article KB312362. By
default, the Memory Manager tries to trim allocated paged pool memory when
the system reaches 80 percent of the total paged pool. Depending on the
system configuration, a possible maximum paged pool memory on a Windows 2003
computer can be 650MB and 80 percent of this number is 520MB. The maximum
paged pool memory for Windows 2000 and XP is 470MB. If the Memory Manager is
unable to trim fast enough to keep up with the demand, you may receive event
ID 2020 (The server was unable to allocate from the system paged pool
because the pool was empty). By tuning the Memory Manager to start the
trimming process earlier (for example, when it reaches 60 percent), it would
be possible to keep up with the paged pool demand during sudden peak usage,
and avoid running out of paged pool memory.\n\nIMPORTANT: The Maximum
(0xFFFFFFFF) PagedPoolSize setting is not recommended for use on 32-bit
Enterprise Edition servers that have 64GB of RAM, as it can potentially
bring the Free System PTE entry down."
----------------------------------------------------------------------------
--
Sometimes the only way to track down the specific resource shortage it is to
force a blue screen and analyse the dump.
. Read Windows Internals 4th Edition by the great Mark Russinovich.
. Have a look at Dmitry Vostokov's sites: DumpAnalysis.org and
TraceAnalysis.org.
Cheers,
Jeremy.
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Dogers
Sent: Tuesday, 29 May 2012 11:17 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Citrix Server Resources Exhausted
Hi Jeremy
That's our suspicion, but we've no idea what to monitor to prove this! We in
the Citrix team have been dying to get onto 2008R2 for a while now (hi Andy
:) ).
And yep, all users use this app (we're actually an ASP). The only real
separation we have is on office versions.
Andrew
Other related posts:
