Increase the speed of access to SharePoint pages w3wp process count and reset recovery

In the previous article we mentioned the pre-loading of the IIS application pool, and today we are going to optimize the process count for w3wp.

We mentioned w3wp this process, this process is actually a user in SharePoint time to access a service process carrier, we can take the user to visit a website process, imagine a customer to the hotel check-in process, IIS application pool has the largest number of connections, The default is 1000, that is, a pool can accept up to 1000 users to connect, the 1001th person who visited the site will be prompted not to access. There is also a queue length, by default, a user visits the site, will be a w3wp process to interact with him, w3wp process you can understand the hotel's front desk staff, by him to help users check-in business. Queue Length can be understood as queue length, only one of the processing, so as to be able to proceed in a normal and orderly manner, no matter after the face of the few people lined up, have to one.

But an application pool, in fact, can correspond to multiple w3wp processes, there will be a number of receptionist to help users check-in, that is, there will be a number of processes to assist in the processing of interactive requests to provide services to users, which naturally improve the site's access efficiency.

For the application pool of SharePoint, we recommend that everyone is mainly for the 80 port of the primary site pool, multi-enable a few w3wp is enough, in the pool to find the number of working processes, it is recommended to set from 2 start, if the memory and CPU sufficient, can be set to 4.

By default, the pool and w3wp are one by one corresponding, we can change to a pair of more. This is the maximum number of worker processes that we can find in the IIS application pool advanced settings, such as.

650) this.width=650; "height=" 497 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M00/8F/07/wKioL1jR4m3AfYU8AAOZE6wqgxE710.png" border= "0"/>

How many processes are enabled, this according to the occupancy rate of the memory of everyone, the daily work if the memory is very high, the value here is not set too high, you can set it to 2 to see the effect, and then as appropriate sliding scale.

And here's a little bit more, by default, the application pool will have an idle recycle operation, and in 20 minutes, if no one accesses the pool, no one will come and collect it.

So here we can make changes by the following two parameters, we recommend that the idle timeout operation to terminate, leisure time-out setting longer, such as 12 hours no one to access, and then to terminate the operation.

650) this.width=650; "height=" 497 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M01/8F/09/wKiom1jR4nCAU1UPAAM3wHa0x70904.png" border= "0"/>

Finally, I want to share with you one of the last things in IIS that need to be optimized-----IIS Reset Recycle

What is reset recycle? In short, it is a taste to prevent pool recycling, user access interruption, by default, the session and memory state are present in the pool, which is to alleviate the burden of SQL, but also brought a problem, since the session in the pool, the pool is recycled, the pool has been restarted, What about our user's session? If the user is in a very important or urgent connection, this process is not allowed to be interrupted, if the pool is recycled, the connection is broken, is not the end of it?

"Reset Recycle" is one of the options we need, as long as we turn on the reset recovery, we can achieve an effect, when the pool is to be recycled, will automatically start a process to take over the current user's request, the session will also reprint the past, to ensure that the user will not be disconnected because of the site recycling. If you do not turn on this reset recovery option, the user's session will be broken when the application pool recycle occurs.

Some do development applications should know this, the session is usually very fastidious, and even sometimes deploy a session server to store the session, do not put the session into memory, the purpose is to prevent the occurrence of such events and users to bring trouble.

You can find this reset recycling option in the advanced options of the application pool, the English version of the user must remember "negative negative is positive" Yo!

650) this.width=650; "height=" 497 "title=" image "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;margin:0px;padding-right:0px; "alt=" image " Src= "Http://s3.51cto.com/wyfs02/M02/8F/09/wKiom1jR4nKgScqLAAN6zIEmytE575.png" border= "0"/>

If there are applications that are heavily dependent on the session, be sure to turn this setting on. This setting is not limited to SharePoint, all of which are valid for connection applications related to IIS.

In fact, SharePoint is okay, in a multi-server farm SharePoint is a shared session mechanism, several front-end Web server sharing session, even if one dropped, the session can be found on other machines. But also do not rule out an extreme situation, that is, multiple front-end Web servers at the same point in time to do the recycling, if so, then the session will be broken, so on the safe side, it is no harm to open a reset recovery.

But it's important to note that if you are a small partner in one single deployment, this option is a priority!

This article is from the "June Ma Run Space" blog, be sure to keep this source http://horse87.blog.51cto.com/2633686/1909113

Increase the speed of access to SharePoint pages w3wp process count and reset recovery