Microsoft Office Tutorials and References
In Depth Information
Optimizing for Performance
ECS CPUs, but not the best utilization of memory. If you have a lot of workbooks, you should not
use this method, because each workbook will likely be opened in the memory of each ECS
machine, will not have enough memory to be cached, and will therefore have an inferior
Workbook URL — This is the default load balancing. The WFEs will always open any workbook
on the same ECS machine. Use this method when there are a lot of workbooks and requests on
them. It will achieve a good utilization of memory, but might not achieve the best utilization of
CPU. For example, if one workbook is accessed much more than the others, the ECS associated
with that workbook will have a much higher CPU usage than the other ECS machines.
As you can see, each method had unique performance characteristics, and no method is optimal for all
cases. Choose the one that best fits your scenario.
Excel Services is a system distributed over multiple machines connected through the network in one of
the following ways:
Connection between the client machines and the WFE
Connection between the WFE, the application server, and the database server
Connection with other servers (such as external databases, SSO servers, or Active Directory servers)
Connection Between Client Machines and the WFEs
There are many factors that affect the performance of the connection between the client machines and the
server. These include the network topology and speed, intranet versus extranet, HTTP versus HTTPS,
firewalls, and load balancing. Some of these might be outside your control, but you should be aware of them
because they impact the response time that your users will experience.
Loading one page of a workbook might require transmitting several hundred kilobytes over the network.
As the designer of the workbook, you can impact this size as follows:
You can reduce the number of rows and columns displayed. For example, a range of 75 rows by
20 columns will contain 1500 cells.
Some features require larger amounts of data. Charts are sent as images to the browser, and the
image size depends on the complexity and size of the chart. Some formatting features (such as
conditional formatting) will send additional data for each relevant cell.
A dashboard that has multiple EWA Web Parts on it will be as large as the sum of the Web Parts.
To reduce the load time of the Web page, you could have a top-level dashboard that contains
only the most important information, and use linked dashboards for additional details.
Secure connections (HTTPS) are slower because they must encrypt the communications. After you have
complete your security analysis (for example, determining how sensitive the information passed over
the network is, who your users are, and how secure the network is), you should balance it against the
performance impact of using the HTTPS protocol.