Exporter (0) Imprimer
Développer tout

Déterminer les besoins en matière de ressources pour la prise en charge d’Excel Services

SharePoint 2007

Mise à jour : 2009-02-26

In this article:

Many factors can affect the performance and availability of your Microsoft Office SharePoint Server 2007 deployment, including network bandwidth and resource consumption. Services Excel dans Microsoft Office SharePoint Server 2007 in Office SharePoint Server 2007 can affect system performance, depending on the volume of client connections and the number of simultaneous Services de calcul Excel session requests. Calculation size and complexity can also affect Services de calcul Excel resource consumption.

The scope and complexity of Excel calculations can affect the performance and availability of Services Excel in an Office SharePoint Server 2007 deployment. As calculation volume, complexity, and frequency increase, more system resources are consumed. Define baseline hardware requirements for system memory, CPU speed, and storage for each application server that runs Services de calcul Excel.

About Excel Services topologies

Office SharePoint Server 2007 is logically divided into three tiers: the front-end Web server tier, the application server tier, and the database tier. During installation, Services Excel installs two components (Excel Web Access and Excel Web Services) on the front-end Web server tier, and one component (Services de calcul Excel) on the application server tier, as shown in the following diagram.

Services Excel : architecture de base

A network load balancer enables Office SharePoint Server 2007 to scale out front-end Web servers. The network load balancer is available to all Office SharePoint Server 2007 applications. You can scale out application servers by adding computers within the shared services framework in Office SharePoint Server 2007.

There are three schemes for load balancing Services de calcul Excel requests: Workbook URL, Round-Robin, and Local. You can configure separate load balancing schemes for each Shared Services Provider (SSP).

For information about how to install the Office SharePoint Server 2007 Services Excel components, see the following articles:

Data access models

There are two data access models you can use for any of the Services Excel server farm topologies: trusted subsystem and constrained Kerberos delegation.

  • Trusted subsystem   This is the default setting for a Windows server farm, because it does not have the extra configuration requirements of the delegation model. In the trusted subsystem model, front-end Web servers and application servers running Services de calcul Excel trust the accounts of the associated Office SharePoint Server 2007 applications by using the SSP. In a trusted subsystem environment, when opening files from Microsoft Office SharePoint Server 2007, permission checks on the files can be performed against end-user identities even if Kerberos is not configured. If Services de calcul Excel application servers are opening workbooks from UNC shares or HTTP Web sites, the user account cannot be impersonated, and the process account must be used.

  • Constrained Kerberos delegation   This is the most secure configuration for communication between front-end Web servers and Services de calcul Excel application servers. Constrained Kerberos delegation is also the most secure configuration for accessing back-end data sources from application servers. Constrained Kerberos delegation is the preferred configuration for deploying Services Excel. For external data connections, Integrated Windows authentication will only work if the delegation model is implemented.

Excel Services topologies

The following Services Excel topologies are described in this section:

Excel Services single-server topology

The following topology diagram shows the logical architecture for a stand-alone Services Excel deployment on a single server.

Services Excel : topologie à serveur unique

In this example, all Office SharePoint Server 2007 components are installed on a single computer. This includes the Services Excel front-end Web server components and Services de calcul Excel, the application server component of Services Excel. This also includes the configuration and content databases, which are installed by using Microsoft SQL Server Express Edition. This topology is useful for testing the core functionality of Services Excel, but it is not recommended as a scalable solution.

This configuration supports multiple Windows SharePoint Services 3.0 Web applications by using Integrated Windows authentication. In this configuration, external data access can be provided by using data connection libraries, the Microsoft Single Sign-On service (SSO), or data connections embedded in workbooks. Load balancing is provided by the Services Excel load–balancing component. This topology uses the trusted subsystem data access method. The file access method is an Services de calcul Excel process account configured as an SSO administrator.

Excel Services small farm trusted subsystem topology

The following topology diagram shows the logical architecture for a small farm Services Excel deployment that uses the trusted subsystem data access model.

Services Excel : topologie pour une batterie de serveurs de sous-système approuvé de petite taille

In this example, the Services Excel front-end Web server components and the application server component are installed on one server, and the SQL Server 2005 configuration and content databases are installed on a separate server. This configuration also shows the Single Sign-On service running on the Office SharePoint Server 2007 server. The configuration also shows the Services de calcul Excel process account configured as an SSO administrator.

Excel Services small farm Kerberos topology

The following topology diagram shows the logical architecture for a small farm Services Excel deployment that uses the constrained Kerberos delegation data access model.

Services Excel : topologie Kerberos pour une batterie de serveurs de petite taille

In this example, the Services Excel front-end Web server components and the application server component are installed on one server, and the SQL Server 2005 configuration and content databases are installed on a separate server. This configuration also shows the Single Sign-On service running on the Office SharePoint Server 2007 server. The configuration also shows the Services de calcul Excel process account configured as an SSO administrator.

Excel Services medium farm trusted subsystem topology

The following topology diagram shows the logical architecture for a medium farm Services Excel deployment that uses the trusted subsystem data access model.

Services Excel : topologie pour une batterie de serveurs de sous-système approuvé

In this example, the Services Excel front-end Web server components, the application server component, and the SQL Server 2005 configuration and content databases are installed on three separate servers. This configuration also shows the Single Sign-On service running on the Office SharePoint Server 2007 front-end Web server and on the Services Excel application server. The configuration also shows the Services de calcul Excel process account configured as an SSO administrator.

Excel Services medium farm Kerberos topology

The following topology diagram shows the logical architecture for a medium farm Services Excel deployment that uses the constrained Kerberos delegation data access model.

Services Excel : topologie Kerberos pour une batterie de serveurs de taille moyenne

In this example, the Services Excel front-end Web server components, the application server component, and the SQL Server 2005 configuration and content databases are installed on three separate servers. This configuration also shows the Single Sign-On service running on the Office SharePoint Server 2007 front-end Web server and on the Services Excel application server. The configuration also shows the Services de calcul Excel process account configured as an SSO administrator.

Excel Services large farm trusted subsystem topology

The following topology diagram shows the logical architecture for a large farm Services Excel deployment that uses the trusted subsystem data access model.

Services Excel : topologie TSS pour une batterie de serveurs de grande taille

In this example, multiple Services Excel front-end Web server components, multiple application server components, and multiple SQL Server 2005 configuration and content databases are each installed on separate servers. This configuration also shows the Single Sign-On service running on the Office SharePoint Server 2007 front-end Web server and on the Services Excel application server. The configuration also shows the Services de calcul Excel process account configured as an SSO administrator.

ImportantImportant :

For large farm deployments, it is recommended to run Office SharePoint Server 2007 in a homogeneous environment. All of the servers in a large farm should run either a 32-bit version of Windows Server 2003 or a 64-bit version of Windows Server 2003. It is not recommended to run Office SharePoint Server 2007 in a mixed environment.

Excel Services large farm Kerberos topology

The following topology diagram shows the logical architecture for a large farm Services Excel deployment that uses the constrained Kerberos delegation data access model.

Services Excel : topologie Kerberos pour une batterie de serveurs de grande taille

In this example, multiple Services Excel front-end Web server components, multiple application server components, and multiple SQL Server 2005 configuration and content databases are each installed on separate servers. This configuration also shows the Single Sign-On service running on the Office SharePoint Server 2007 front-end Web server and on the Services Excel application server. The configuration also shows the Services de calcul Excel process account configured as an SSO administrator.

Excel Services extranet topology

The following topology diagram shows the logical architecture for Services Excel front-end Web server components, application server components, and SQL Server 2005 configuration and content databases deployed in a perimeter network.

Services Excel : besoins en ressources extranet

In this example, Services Excel components are isolated from external data sources and client computers in a secure perimeter network behind firewalls. This configuration provides enhanced security for data sources and helps prevent data corruption and unauthorized access to data.

NoteRemarque :

If you have a Windows firewall enabled on the application servers, you must open the specific port on which the shared services Web site that hosts Services de calcul Excel is running.

Excel Services corporate intranet topology

The following topology diagram shows the logical architecture for an Services Excel deployment that isolates front-end Web server components and SQL Server 2005 configuration and content databases in a perimeter network that is separated from the corporate intranet. Services Excel application servers are deployed within the corporate intranet and all Services Excel components are isolated from remote client computers and from external data sources.

Services Excel : topologie d’intranet d’entreprise

In this example, Services Excel application servers are deployed within the corporate network and are protected from direct external access. This configuration enables you to tightly control who can access your application servers and data. By isolating front-end Web servers in a perimeter network, you limit the attack surface of your environment to public-facing Web servers.

NoteRemarque :

If you have a Windows firewall enabled on the application servers, you must open the specific port on which the shared services Web site that hosts Services de calcul Excel is running.

Excel Services high-performance computing topology

The following topology diagram shows the logical architecture for a deployment that includes Microsoft Windows Compute Cluster Server 2003 and Services Excel.

Services Excel : planification des besoins en ressources

In this example, the Services Excel front-end Web server components and the application server component are installed on individual compute cluster nodes that comprise a compute cluster. These nodes share a SQL Server 2005 configuration and content database that runs on a server that is external to the compute cluster. A head node runs the compute cluster scheduler that schedules and load balances jobs among the nodes in the cluster.

Plan for simultaneous client connections

The number of simultaneous client connections can impact the performance and availability of front-end Web servers. For a deployment designed to support a large number of client connections, you need to plan for the deployment of enough front-end Web servers to support an adequate level of system performance and availability. Determine the number of front-end Web servers that are required for your deployment scenario. Define baseline hardware requirements for system memory, CPU speed, and storage for each front-end Web server.

Plan for concurrent Excel Calculation Services session requests

To determine the appropriate scale of a deployment to support Services de calcul Excel in Office SharePoint Server 2007, you need to know how many concurrent Services de calcul Excel session requests the scenario needs to support. For a deployment designed to support a large volume of Services de calcul Excel sessions, you need to plan for enough Services de calcul Excel servers to support an adequate level of performance and availability. Add Services de calcul Excel servers to improve performance and availability. Services de calcul Excel Proxy is a front-end Web server component used to load-balance session requests among the available application servers that run Services de calcul Excel.

You can configure a per-user session limit for application servers that run Services de calcul Excel. This value is the maximum number of concurrent sessions allowed for each user. Windows SharePoint Services 3.0 Web sites can be configured to allow anonymous user access. In this case, the Services de calcul Excel session limit for a single user will still apply. All anonymous users share the same session limit value that is configured for a single user.

The following configuration changes are recommended for an Services Excel environment that supports a large volume of Services de calcul Excel session requests and workbook calculations.

  • IIS time-out   If calculations in Services Excel are expected to take longer than 110 seconds, increase the IIS time-out value. A ThreadAbort exception will occur when calculations exceed the IIS time-out setting. The default IIS time-out setting is 110 seconds.

  • ASP.NET MaxConnection   When the number of client connection requests requires front-end Web servers to open multiple concurrent connections to application servers running Services de calcul Excel, you need to increase the maximum number of ASP.NET connections. In ASP.NET, configure the MaxConnection setting to a maximum connection limit of 10, as shown in the following example:

    <configuration>
       <system.net>
          <connectionManagement>
             <add address="*" maxconnection="10" />
          </connectionManagement>
       </system.net>
    <system.web>
    

Consider configuring the following Windows Server 2003 registry settings to improve Services de calcul Excel performance.

CautionAttention :

Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

  • HeapDeCommitFreeBlockThreshold   During a period when Services de calcul Excel application servers are experiencing a high volume of requests, the application servers might encounter performance issues caused by memory allocation failures. Because of memory fragmentation, this can occur even if application servers have adequate amounts of RAM installed to handle the volume of requests. To alleviate this problem, use the Registry Editor to change the HeapDeCommitFreeBlockThreshold setting to REG_DWORD 0x00040000. To change the setting, use the following registry path:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

  • MaxUserPort   You might need to increase the range of available ports by changing the value of the MaxUserPort registry setting. The MaxUserPort setting specifies the highest port number that TCP can assign when an application requests an available user port from the system. To change this registry setting, run the Registry Editor and use the following registry path:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

  • TcpNumConnections   You might need to increase the maximum number of connections that TCP can have open simultaneously by changing the value of the TcpNumConnections registry setting. If the TcpNumConnections registry key does not exist, run the Registry Editor to create and configure the key. To change this registry setting, run the Registry Editor and use the following registry path:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

  • TcpTimedWaitDelay   During a period when Services de calcul Excel application servers are experiencing a high volume of requests, there is a possibility that some requests will be denied. If this occurs, you might be encountering a problem with the default setting of the TcpTimedWaitDelay registry key. By default, the TcpTimedWaitDelay setting is set to 240 seconds, or four minutes. This is the amount of time that must elapse before a closed TCP session can be released and the resources can be reassigned. To alleviate this problem, use the Registry Editor to change the TcpTimedWaitDelay setting from 240 seconds to 30 seconds. If the TcpTimedWaitDelay registry key does not exist, run the Registry Editor to create and configure the key by using the following registry path:

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Services\Tcpip\Parameters

Excel Services performance testing

The following performance test results provide guidance based on comparisons of throughput, response times, and resource utilization of Services Excel by using different topologies and data sets. These recommendations are also based on comparisons of performance factors by using different external data authentication schemes for online analytical processing (OLAP) and relational external data connections. Resource requirements and response times in Services Excel depend on workbook size, workbook complexity, the number of concurrent users, and external data latency. Tests are run by using a defined data set, and results vary depending on data set design.

The baseline configuration for each tested data set includes Office SharePoint Server 2007 dashboards, with each dashboard rendering two Excel Web Access Web Parts and two key performance indicator (KPI) Web Parts. The result is four Services de calcul Excel sessions for each page hit.

Twenty percent of the sessions are assumed to have some interactivity, such as paging or data refresh. The tests are based on the assumption that 5,000 users are actively accessing dashboards and portal KPIs linked to cells in Microsoft Office Excel 2007 workbooks.

Hardware configuration

Performance testing was run on Office SharePoint Server 2007 front-end Web servers, Services de calcul Excel application servers, and Office SharePoint Server 2007 SQL Configuration and Content Database servers with the following hardware configurations:

Servers Hardware configuration

The Office SharePoint Server 2007 front-end Web servers

Two Dual-Core AMD Opteron 275 CPUs running at 2.2 GHz, with 9.83 GB RAM

The Services de calcul Excel application servers

Two Dual-Core AMD Opteron 275 CPUs running at 2.2 GHz, with 9.83 GB RAM

The Office SharePoint Server 2007 SQL Configuration and Content Database servers

Four Dual-Core AMD Opteron 880 CPUs running at 2.4 GHz, with 8 GB RAM

Data set attribute tables

This section provides information about the attributes of the data set and scenarios used for performance testing. Exceptions to these attributes are noted in individual configurations, as applicable. Services Excel performance depends on the attributes of the data set, including memory usage, CPU usage, throughput, and response time. It is important to consider the characteristics of your data set before using the performance test results provided here. The results you get will vary based on the data used in your environment, and other variables.

Performance test scenarios

The performance tests were run using the following test scenarios. The scenarios are based on an assumption of a total of 5000 users actively accessing dashboard pages and Excel workbooks, with Office Excel Web Access. The scenarios are also based on the assumption that a variety of dashboards are accessed with varying degrees of frequency. The tests include:

  • A small number of dashboards that are accessed frequently by a large number of users.

  • A large number of dashboards that are accessed infrequently by a small number of users.

This range of dashboard usage corresponds to an enterprise environment in which a small number of dashboards are used across the entire organization, and a large number of dashboards are used by groups within the organization.

Number of users Frequency of views Number of dashboards Number of workbooks

3,750

Twice a day

5

10

1,500

Three times a week

25

24

1,000

Once a week

50

50

250

Once a month

150

40

150

30% of 1,000 files are viewed by users accessing Excel Web Access Web Parts

300

25

Workbooks without external data connections

The workbooks in this scenario are not connected to an external data source. Resource consumption is determined by the size, complexity, the amount of formatting, and the number of calculations used in each workbook. Workbook size is determined by the number of rows and columns each workbook contains. All of these factors affect resource consumption and throughput in Services Excel. The workbooks include a range of features, such as formatting, conditional formatting, and charting. The dataset used includes a range of workbooks with the following attributes:

Percentage of workbooks Rows Columns Percentage of calculations Percentage of formatting Volatile functions

2%

<5,000

10 – 45

50%

50%

Yes

38%

<5,000

10 – 45

20%

50%

No

5%

<5,000

60 – 365

5%

50%

No

20%

5,000 – 7,000

10 – 40

10%

50%

No

15%

7,001 – 10,000

10 – 50

10%

50%

No

15%

10,001 – 15,000

10 – 50

10%

50%

No

5%

15,001 – 20,000

10 – 50

10%

50%

No

Workbooks with OLAP data connections

The workbooks in this scenario contain data connections to Analysis Services cubes. These workbooks include a range of features, such as formatting and conditional formatting. In addition to the variables that affect resource consumption and throughput in every scenario, the amount of Analysis Services data that is consumed by the workbooks in this scenario, and whether or not the workbooks are refreshed on open, can affect Services Excel performance. This scenario is based on the assumption that 15% of the workbooks have data connections that refresh on open. Caching has a major impact on the performance of external data connections. Typically, Services Excel uses cached data if there is a connection to an external data source, using the same credentials multiple times. Caching performance is also affected by the Services Excel External Data Cache Lifetime setting.

Percentage Rows Row size Other

10%

<1,000

512 – 2,048

DCL SSO (or Kerberos)

20%

<1,000

512 – 2,048

DCL SSO (or Kerberos), refresh on open

40%

<1,000

100 – 512

One to four PivotTable reports and one to four PivotChart reports embedded in workbooks

20%

<1,000

<100

Four to six PivotTable reports and four to six PivotChart reports embedded in workbooks

10%

1,000 – 5,000

<100

Two PivotTable reports and two PivotChart reports embedded in workbooks

Workbooks with relational data connections

The workbooks in this scenario contain data connections to SQL Server relational databases. These workbooks include a range of features, such as formatting and conditional formatting. In addition to the variables that affect resource consumption and throughput in every scenario, whether or not the workbooks are refreshed on open can affect Services Excel performance in this scenario. This scenario is based on the assumption that 15% of the workbooks have data connections that refresh on open. Caching has a major impact on the performance of external data connections. Typically, Services Excel uses cached data if there is a connection to an external data source, using the same credentials multiple times. Caching performance is also affected by the Services Excel External Data Cache Lifetime setting.

Percentage Rows Row size Other

2%

<1,000

<512

DCL SSO (or Kerberos), periodic refresh

20%

<500

<512

DCL SSO (or Kerberos), refresh on open

40%

1,001 – 5,000

1024 – 2,048

One or two PivotTable reports and one or two PivotChart reports embedded in workbooks

20%

5,000 – 10,000

1024 – 2,048

DCL SSO; one or two PivotTable reports and one or two PivotChart reports embedded in workbooks

10%

10,000 – 20,000

512 – 1,024

DCL SSO; two to four PivotTable reports and two to four PivotChart reports embedded in workbooks

8%

20,000 – 65,000

<512

DCL SSO; one or two PivotTable reports embedded in workbooks

Distribution of workbooks by data sources

Performance tests were run using the following distribution of workbooks. Exceptions to this distribution are noted for some of the configurations. In each configuration, workbooks were distributed based on the percentages shown in the data set attribute tables. For Example, 30% of the workbooks contained no external data. Of these, 20% had between 5000 and 7000 rows, as shown in the Workbooks without external data connections table. This resulted in 6% of the total workbook distribution (20% of 30%), consisting of workbooks with no external data and containing between 5000 and 7000 rows. Some of the configurations isolate workbooks of a specific type. For example, workbooks containing OLAP data connections configured to refresh on open.

Workbook type Percentage

Workbooks with no external data

30%

Workbooks with OLAP data connections

35%

Workbooks with relational data connections

35%

Request mix used in performance tests

Performance tests were run using the following request mix. There are exceptions to this request mix. For example, in tests using workbooks with no external data, there are no interactive operations with external data queries. Exceptions are noted for some of the configurations.

Request type Percentage of total requests

OpenWorkbook (includes one GetRrange)

65%

Interactive requests with external data queries

15%

GetRange (paging)

10%

Find, Sort, and Filter interactive requests within workbooks

10%

Performance test results

The tables in this section show test results for each tested configuration.

Excel Services small farm trusted subsystem configuration

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with no external data

30%

Workbooks with OLAP data connections

35%

Workbooks with relational data connections

35%

The following table shows front-end Web server test results for this configuration:

Performance counter Result

Requests per second

14.32

Average response time in seconds

5.52

ASP.NET queue

1.91

CPU

41.97

W3wp process private bytes

822

The following table shows Services de calcul Excel application server test results for this configuration:

Performance counter Result

Requests per second

15.52

Average response time in seconds

2.05

Sessions per second

2.94

ASP.NET queue

1.91

CPU

41.97

W3wp process private bytes

3844

Excel Services large farm trusted subsystem configuration

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with no external data

30%

Workbooks with OLAP data connections

35%

Workbooks with relational data connections

35%

The following table shows front-end Web server test results for this configuration.

Performance counter Front-end Web server 1 Front-end Web server 2 Front-end Web server3

Requests per second

4.62

4.54

4.63

Average response time in seconds

10

9.69

10.01

ASP.NET queue

0.12

0.2

0.25

CPU

1.13

1.21

1.21

W3wp process private bytes

738

713

742

The following table shows Services de calcul Excel application server test results for this configuration.

Performance counter Result

Requests per second

14.8

Average response time in seconds

4.74

Sessions per second

2.58

ASP.NET queue

33.29

CPU

37.84

W3wp process private bytes

3867

Excel Services large farm Kerberos configuration

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with no external data

30%

Workbooks with OLAP data connections

35%

Workbooks with relational data connections

35%

The following table shows front-end Web server test results for this configuration.

Performance counter Front-end Web server 1 Front-end Web server 2 Front-end Web server3

Requests per second

15.39

15.36

15.58

Average response time in seconds

4.48

4.3

4.35

ASP.NET queue

0.46

0.5

0.45

CPU

4.43

4.33

4.36

W3wp process private bytes

906

909

899

The following table shows Services de calcul Excel application server test results for this configuration.

Performance counter Result

Requests per second

46.36

Average response time in seconds

1.36

Sessions per second

9.43

ASP.NET queue

63.55

CPU

54.82

W3wp process private bytes

6387

Excel Services large farm trusted subsystem configuration using OLAP data with refresh on open and SSO

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with OLAP data connections; refresh on open; uses SSO for external data authentication

100%

The following table shows front-end Web server test results for this configuration:

Performance counter Front-end Web server 1 Front-end Web server 2 Front-end Web server3

Requests per second

1.84

1.83

1.85

Average response time in seconds

7.6

7.5

8.07

ASP.NET queue

0.001

0.001

0

CPU

0.59

0.61

0.62

W3wp process private bytes

379

375

384

The following table shows Services de calcul Excel application server test results for this configuration:

Performance counter Result

Requests per second

6.52

Average response time in seconds

3.82

Sessions per second

1.08

ASP.NET queue

1.22

CPU

45.29

W3wp process private bytes

4995

Excel Services large farm Kerberos configuration using OLAP data with refresh on open

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with OLAP data connections; refresh on open; uses Kerberos for external data authentication; user credentials are delegated for authentication with OLAP data sources

100%

The following table shows front-end Web server test results for this configuration.

Performance counter Front-end Web server 1 Front-end Web server 2 Front-end Web server3

Requests per second

0.99

1

0.99

Average response time in seconds

19.29

18.32

19.36

ASP.NET queue

0.001

0

0.001

CPU

0.41

0.41

0.38

W3wp process private bytes

417

431

425

The following table shows Services de calcul Excel application server test results for this configuration.

Performance counter Result

Requests per second

2.95

Average response time in seconds

17.39

Sessions per second

0.59

ASP.NET queue

11.63

CPU

54.8

W3wp process private bytes

10419

Excel Services large farm Kerberos configuration using SQL Server 2005 Analysis Services groups

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with OLAP data connections; refresh on open, using Kerberos for external data authentication; user credentials are delegated for authentication with OLAP data sources; users map to SQL Server 2005 Analysis Services groups

100%

The following table shows front-end Web server test results for this configuration.

Performance counter Front-end Web server 1 Front-end Web server 2 Front-end Web server3

Requests per second

8.7

8.38

8.62

Average response time in seconds

3.63

3.69

3.7

ASP.NET queue

0.004

0.004

0.006

CPU

2.31

2.31

2.3

W3wp process private bytes

435

431

452

The following table shows Services de calcul Excel application server test results for this configuration.

Performance counter Result

Requests per second

25.67

Average response time in seconds

1.69

Sessions per second

5.22

ASP.NET queue

2.73

CPU

63.07

W3wp process private bytes

7850

Excel Services large farm trusted subsystem configuration using relational data

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with relational data connections; refresh on open, using SSO for external data authentication

100%

The following table shows front-end Web server test results for this configuration.

Performance counter Front-end Web server 1 Front-end Web server 2 Front-end Web server3

Requests per second

24.07

24.2

24.6

Average response time in seconds

3.17

3.16

3.15

ASP.NET queue

9.15

10.41

13.77

CPU

6.49

6.65

6.78

W3wp process private bytes

959

965

1062

The following table shows Services de calcul Excel application server test results for this configuration.

Performance counter Result

Requests per second

76.16

Average response time in seconds

0.43

Sessions per second

14.84

ASP.NET queue

17.79

CPU

46.62

W3wp process private bytes

35.88

Excel Services large farm Kerberos configuration using relational data

The following table shows the data set for this configuration.

Workbook type Percentage

Workbooks with relational data connections; refresh on open, using constrained Kerberos delegation for external data authentication

100%

The following table shows front-end Web server test results for this configuration.

Performance counter Front-end Web server 1 Front-end Web server 2 Front-end Web server3

Requests per second

22.78

22.6

23.1

Average response time in seconds

3.03

2.97

2.98

ASP.NET queue

0.59

0.5

0.39

CPU

6.18

6.15

6.16

W3wp process private bytes

836

838

843

The following table shows Services de calcul Excel application server test results for this configuration.

Performance counter Result

Requests per second

68.41

Average response time in seconds

0.74

Sessions per second

13.87

ASP.NET queue

21.46

CPU

55.87

W3wp process private bytes

6328

Limit the number and duration of open sessions

In addition to adding resources, limiting the number of open Services de calcul Excel sessions can help mitigate performance and availability issues. One way to limit the number of open Services de calcul Excel sessions is to decrease session time-out settings. Indiscriminately limiting session duration can cause active sessions to close, which can result in data loss.

The preferred solution is to use Office Excel Web Access Short Session Mode to configure shorter initial time-out settings for sessions that have no client-side interactivity when the sessions are opened. You can configure a second time-out setting for sessions that are active as soon as they are opened. In this example, sessions that remain inactive for the duration of the initial time-out setting are closed by the Services de calcul Excel server. Sessions that are active before the initial time-out setting expires will remain open until the second time-out setting expires.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Downloadable content for Office SharePoint Server 2007.

Voir aussi

Cela vous a-t-il été utile ?
(1500 caractères restants)
Merci pour vos suggestions.
Afficher:
© 2014 Microsoft