How to understand Excel load balancing

Steve Duris, a project manager for the Excel service team, talked about various Excel load balancing programs that can be used in Excel Services.

I have received some questions in the last few weeks the load Balancer government can choose the Excel service custom load balancer. This is the scoop: the first time you access the Excel service when you set the account Openworkbook method. Once you have an active meeting, workbook, additional requirements, the user will always be sent to the elite for "Openworkbook" requests to deal with.

So why do we have three options-book URLs, rotations, and places? The aim of this approach is to provide administrators with better control over the resources used by his/her farm. Explain each option as follows:

Book URL: It can be said that this provides the most efficient use of your hardware. Please send WFE from an elite based hash URL. This will ensure that the same elite will always handle requests to the same workbook-regardless of user request. This means that the book will only ever be retrieved once from SharePoint-until it squeezes out the cache, or the file changes in S harepoint.

Rotary: Openworkbook requires each to go to the next elite rotation. The result is the same World Bank can be loaded from SharePoint n times, where n = number of elite machines on your farm. Please remember two things: (1) The request for an active meeting will be returned at any time to the same elite, and (2) if the World Bank is a cached elite, when the Openworkbook request arrives, it will be loaded from the cache provided files are not changed in SharePoint. The benefit of this approach is that each concurrent request to a different server, therefore, theoretically, the queuing server (processor, I/O) will be short, so the requirement can be handled more efficiently. The validity of this is due to the composition of the workbook (the work breakdown structure has very long running computations often ineffective this).

Local: This setting ensures that elite processing occurs at the same wfe receiving machine requirements, which requires elite services to be running every wfe. Similarly, with the World Bank can be loaded n times, where n = number of Elite/WFE machine farms. The advantage here is that, theoretically, performance. By running the elite's WFE, reducing the # server to the server hops, end users should have faster performance. Cost is the appropriate potential for retrieving from SharePoint and cache size, while the bank opens multiple wfes.

As you can see, there are pros and cons for each option. However, with the above information, as well as some knowledge and experimentation around you, you should be able to properly select the appropriate load balancing option for the installation.

The above content is by Officeba for you to translate from the foreign language material! For reference only