NTLM verification performance issues after custom SharePoint pages

A strange performance problem found in a project recently. After customizing the master page, even if nothing is changed, the performance of the SharePoint slave page is greatly reduced.

After testing a series of scenarios, we will not go into detail about the strange things.

 

Typical examples:

1. the IIS failed request log shows many pages and page resource files of Large Time (> 3 S). These are all random and irregular.

The following errors are displayed in log,

1. Error 404
2. NTLM authentication takes a long time (> 2 S)
3. Page and page resource file loading time is too long (> 4 S)

2. the ULS log shows that the processing time is normal (about 100 ms.

 

Finally, I found Microsoft premier support, captured n more logs and dump, and gave a magic kb.

You are intermittently prompted for credentials or experience time-outs when you connect to authenticated services

Http://support.microsoft.com/kb/975363

 

1. Start Registry Editor.
2. Find the following registry subkeys:

   HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ netlogon \ Parameters

3. Create the following registry key:
   Name:Maxconcurrentapi
   Type:REG_DWORD
   Value:Set this value to a large number. You can test it (any number greater than the default value ).
4. Run net stop netlogon at the command prompt and then run Net start netlogon.

 

After the concurrency is changed to 40 (adjusted according to the machine performance), the stress test results are significantly improved.

24-core of the machine, 50% GB memory, can actually press the CPU to more than 150, RPs increased from 40 to +, page response time reduced from an average of 5S to about 1-2 seconds.

 

Microsoft's cheating tools are amazing.

 

In addition, why does this problem not occur on the default page? What is amazing? This is still an unsolved mystery.