Today I am sharing a case study for Excessive usages of threads on session expiration processing in Sitecore 9.2 XP and Sitecore 9.2 XC deployments.
Root cause for the issue:
Due to an issue in Session State providers during high load situations, Sitecore instance may end up in a thread starvation issue which can cause the website to become unresponsive.
Solution to the issue:
Sitecore has provided SC Hotfix 367157-1.zip hotfix which is recommended to apply to all Sitecore 9.2 XP and Sitecore 9.2 XC deployments.
The patch should be installed on CD instances (or on servers that are dedicated for handling session expiration, if those are a part of a custom setup).
Today I am going to introduce my new Module for Sitecore Azure PaaS. This module is called Azure Worker Exchanger details for this are as below.
What is Azure Worker Exchanger?
Azure Worker Exchanger Module is a facility created in association with Microsoft Azure Worker API to kill and replace any of the corrupt or non-performing workers created in Azure PaaS. This module should be used only when any worker process is showing a spike in performance and behaving abnormally or got corrupted, to analyze these below are the symptoms.
- Website loading slowly.
- Some of the users are not able to visit the website.
- Azure is throwing many alerts for performance issues.
- Azure matrics showing spikes for performance.
How to use this Module?
- Download the Module here.
- Install on CM role with Sitecore Package Installer.
- Once done you can navigate to the below URL to find the Form.
- Once the form is open you need to supply few details about your Azure Web app. (These are very simple and exactly as mentioned in below photo)
- Once you filled the form submit it.
- You will get a response message back.
- After that wait for 5-10 minutes for Azure to settle everything.
- Once everything is settled you need to go to the Azure Web app and open a kudu to see a new worker created with new underlying resources.
Happy Learning !! Keep Learning !!
Today I am going to explain quick learn for usage of Pre-complied view in Sitecore 9XP. Enabling Pre-compiled MVC views gives boost to performance in Azure PaaS environment, it is considered as one of the performance tuning parameter in Sitecore Azure PaaS environment and Sitecore Managed Cloud.
By pre-compiling views you will benefit from the following:
- Compile time checking of errors. Usually, Razor files are compiled when they are first required. By pre-compiling your Razor views you remove the source of runtime bugs.
- Faster load time. The SitecoreRazorViewEngine will start to load your views from an assembly (.dll file) rather than a view (.cshtml file).
- Once the Razor-Generator is Configured for your Visual Studio Solution you can follow below steps
- To enable Razor-Generator Check this link.
Perform the following to pre-compile MVC views:
- Go to the below folder path. wwwroot\youewebsitefolder\App_Config\Sitecore\Mvc
- Here you will find the config file with the name “Sitecore.Mvc.config”
- In this file search for term “<precompilation>”.
- And under <precompilation> node add below configuration highlighted in green. don’t forget to change the name to your assembly name. <precompilation>
<assemblyIdentity name=”Sitecore.Mvc” />
<assemblyIdentity name=”YourAssemblyName” />
Happy Learning Sitecore !!!!