[THIN] Re: Slightly OT - Trend Performance
- From: "Jay P. Moock" <jmoock@xxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Wed, 11 Jul 2007 11:39:38 -0400
The second part of the answer I posted was something I received from
another person working another case w/ trend, possibly on a non-Citrix
server. I passed it along as a FYI for what the change did. I should
have edited out the extraneous info I guess....
Anyway, no, our servers are still running like crap. Seems to mostly
impact the older Xeon procs w/ hyperthreading. Our newer dual core
boxes don't skip a beat with Trend turned on.
The main thing we notice is much higher than normal kernal times in Task
Manager. Proquota.exe (we enforce a size limit on roaming profiles)
also seems to be at the top of the CPU usage lists, and before the new
engine it was hardly noticed.
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of erik blom
Sent: Wednesday, July 11, 2007 10:36 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Slightly OT - Trend Performance
Jay,
Any noticeable improvements with this fix? Trend's answer states that no
terminal services were installed on your server where the debug logs
came from. Is this correct? Have you implemented this fix on your Citrix
environment?
Regards,
Erik
2007/7/10, Jay P. Moock <jmoock@xxxxxxxxxxxxxxxxx>:
Here's trends explanation of this setting.
---
What is system mapped view?
System mapped views are the kernel-mode virtual memory space. In
general, only the kernel-mode graphics drivers (Win32k.sys) will
use the
region of system mapped views.
Why VSAPI 8.5 uses system mapped view?
Because the size of pattern file nowadays is getting bigger and
for some
memory limited machines, system may not provide enough memory
space to
operate VSAPI. To utilize memory space better, VSAPI will
exploit
half(the maximum) free system mapped views in kernel memory and
it's by
default. Also, a flag in registry was implemented to disable it
in case
some specific system conditions can not benefit from this extra
memory
space.
Root cause analysis:
After analyzed the related debug logs from customer, we
summarized the
following information we have noticed.
1. There was no Terminal Service been installed.
2. Some of the applications which ran on this system used
special
account other than "LocalSystem".
3. The non-interactive desktop heap was changed from 512
KB(system
default) to 3 MB.
According to Microsoft's
blog("http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-
overview.aspx") and it's also proofed from our internal
testing. The
system memory consumption scenario will be :
1. The desktop heap allocations will be made from a fixed 48 MB
region
for system mapped views.
2. Each service which was launched by application and used
special
account will allocate the individual non-interactive desktop
heap.
From the desktop heap monitor tool's log, the sum of all desktop
heap
allocation plus the system mapped views which was allocated by
VSAPI was
over 48MB. So, it resulted in insufficient non-interactive
desktop heap
and application failed to continue the allocation.
Solutions:
We consider the above memory consumption scenario is the special
system
condition. So, the solution is to disable the usage of system
mapped
views in VSAPI 8.5 to give all space for desktop heap allocation
and
it's no any side effect to apply this solution.
The disable approach is to add registry value
"DisableSystemView" to "1"
under HKEY_LOCAL_MACHINE
\System\CurrentControlSet\Services\VSApiNt\Parameters.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Jay P. Moock
Sent: Tuesday, July 10, 2007 7:33 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Slightly OT - Trend Performance
We received the following recommendation from Trend and
implemented it
on one server so far. No useful stats as of yet. Has anyone
else
received/tried this? I didn't see anything in their KB about
this
registry value.
---
On your Citrix server where ServerProtect is having issue with
the
engine, try to add this registry value
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VsapiNT\Parameters
]
Dword: DisableSystemView
value: 1
If it is ok, try to reboot the machine after doing this
procedure. Then
observe the behavior or the performance of SPNT after adding the
key.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:
thin-bounce@xxxxxxxxxxxxx <mailto:thin-bounce@xxxxxxxxxxxxx> ] On
Behalf Of Erik Blom
Sent: Wednesday, July 04, 2007 8:55 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Slightly OT - Trend Performance
We are having the exact same issue too, same engine, same
ServerProtect
version. Made a call to Trend.
These are the kind of issues they should be putting in their KB,
I
think. Looked there, found nothing.
SBC SITES ONLY GOOGLE SEARCH: http://www.F1U.com
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or set Digest or
Vacation
mode use the below link:
//www.freelists.org/list/thin
************************************************
SBC SITES ONLY GOOGLE SEARCH: http://www.F1U.com
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************
Other related posts:
