01: Network Load Balancer Monitoring – Ensure that the monitoring site is not Status.aspx
and instead uses http://servername/personalizationserver/session.aspx
and instead uses http://servername/
02: %ProgramFiles%\AppSense\Environment Manager\Personalization Server\App_Code\Global.asax.cs - Find the first line 'Protocol.IsCompatible = IsCompatibleTypeEnum.Incompatible;' and rem it out (//). Ensure this is the same on each of the Personalization Servers. After the change either reboot the server or restart the PersonalizationServer website.
03: %ProgramFiles%\AppSense\Environment Manager\Personalization Server\web.config - Search for the line 'compilation debug' and ensure that the line reads 'compilation debug="false"'.
04: Auto Close - On the PersonalizationServer database the 'default' setting is to have autoclose ON. This can cause performance degradation. You can check the configuration by executing the following SQL within Management Studio:
SELECT * FROM sys.databases WHERE DATABASEPROPERTYEX(name, 'IsAutoClose') = 1
This will give you a list of all databases which have AutoClose turned on. You can then disable Auto Close by executing:
ALTER DATABASE [PersonalizationServer] SET AUTO_CLOSE OFF WITH NO_WAIT
This can also be done this through the GUI if desired (right click the database > Properties > Options > Auto Close)
If this option is taken to change the database to AutoClose = Off the Personalization SCU will return a variance.
05: IIS Queue Length - You can essentially follow the guide found on http://technet.microsoft.com/en-us/library/dd441171(office.13).aspx which explains how to change the queue length depending on the IIS version. Ideally this needs to be set to around 1.5 times the number of concurrent users.
06: PersonalizationServerPool – Ensure that the pool has only ‘1’ worker process.
No comments:
Post a Comment