Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

100% CPU - Logging of layer activation / deactivation

Created: 08 Dec 2011 | 2 comments
Switact's picture
+1 1 Vote
Login to vote

L.S.

 

Using SWV 6.1 SP7, we still experiance 100% CPU sometimes. To summarise:

- when some layers are active, sometimes the CPU usage spike's to 100% (of one or more cores).

- (one of) the problem register key('s) is HKEY_USERS\USER_TEMPLATE\Software\Classes\Local Settings\MuiCache. This can be deleted from the layer.

- after deactivating ALL active layers, the CPU hog is gone. (not just the layer with this key).

- mostly all layers can be reactivated without problems.

 

With over 100 layers, it's a lot off work to check them all. I would like to know when which layer is activated, so when I hear about the 100% CPU problem afterwards (mostly the system is already rebooted when I hear about is), I can check some log (eventlog / file) to discover wich layers where active at some point in time. Then I can focus on the active layers when the problem occurs.

 

Is there some logging, or can it be activated, about the activation (and deactivation) of layers?

 

Thomas Roes

Comments

erikw's picture
09
Dec
2011
0 Votes 0
Login to vote

CPU HOG

We are struggling with this as well.

What we actually saw is evalauted by one of my employees and this is what he found.

For every “Activate” call that is made the WmiPrvSE process starts scanning the registry entries below “HKLM\System\CurrentControlSet\services\FSLX\Parameters\FSL” to enumerate the present registered layers.

After enumerating approximately between 700 and 800 entries (where 2 entries represents 1 application layer) the enumeration process starts from scratch reading between 2 and 5 entries more every time it restarts enumerating.
After enumerating finally completes, the actual activation takes place.
 
For a repository containing only 1 (one) average application layer, activating takes around 1 (one) second and WmiPrvSE generates around approximately 1.800 registry calls (depending on size and contents of the layer).
But using a repository containing 500 application, WmiPrvSE generates approximately 800.000 registry calls per layer and activating the first layer goes fast, but the more layers are already activated, the slower a new layer activation is processed (up to 5-10 seconds per layer depending on size and contents).

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

Switact's picture
15
Dec
2011
0 Votes 0
Login to vote

Hi,   I started another

Hi,

 

I started another topic, trying to reduce not a temporary but a static CPU hog. It's mainly about cleaning up layers. Please check

 

https://www-secure.symantec.com/connect/forums/layer-cleanup-best-praktise

 

Thomas Roes