Capacity planning for Duet Enterprise for SharePoint and SAP Server 2.0
Applies to: Duet Enterprise for Microsoft SharePoint and SAP Server 2.0
Summary: Learn about planning for capacity limits and recommended practices for Duet Enterprise 2.0.
This article contains capacity planning guidance for Duet Enterprise for Microsoft SharePoint and SAP Server 2.0. It describes software boundaries and limits of Duet Enterprise 2.0, recommendations based on performance test results, and provides links to information that help you plan capacity for Duet Enterprise 2.0.
In this article:
Plan capacity
Plan capacity for collaboration sites
Plan for boundaries and limits
Plan for reporting and workflow features
Plan capacity
The capacity limits and recommended practices for Duet Enterprise for Microsoft SharePoint and SAP Server 2.0 are the same as they are for SharePoint Server 2013. To plan capacity for Duet Enterprise 2.0, you can review the information in the Test results and recommendations section later in this article, and use the capacity planning documentation that is available for SharePoint Server 2013. For more information, see Capacity planning for SharePoint Server 2013 and Plan for performance and capacity management in SharePoint Server 2013.
Plan capacity for collaboration sites
When you create site collections and subsites used as collaboration workspaces, performance can degrade if the number of site collections that are created in a single site collection is too great. The recommended maximum number of site collections per web application for SharePoint Server 2013 is 250,000. The recommended maximum number of collaboration sites that can be created in a site collection with Duet Enterprise 2.0 is 25,000.
The earlier version of Duet Enterprise provided the Duet Enterprise Customers site template and Duet Enterprise Products site template for creating collaboration workspaces. These site templates are still provided with Duet Enterprise 2.0. However, you can use them with Duet Enterprise 2.0 only if you are connected to SAP by using SAP SOAP Services. These templates do not work with OData services, which is the recommended way to connect to SAP NetWeaver. If you want to use collaboration workspaces with OData services, you must create custom collaboration workspaces.
Plan for boundaries and limits
This section describes software boundaries and limits of Duet Enterprise 2.0. These include the following:
Boundaries: Static limits that cannot be exceeded by design.
Thresholds: Configurable limits that can be exceeded to accommodate specific requirements.
Supported limits: Configurable limits that have been set by default to a tested value.
For more information about boundaries and limits, see Software boundaries and limits for SharePoint 2013.
The following table lists the recommended guidelines for Duet Enterprise 2.0.
| Limit | Maximum value | Limit type | Notes |
|---|---|---|---|
Number of attachments in a workflow task |
10 |
Boundary |
|
Size for an attachment in a workflow task |
14 MB |
Boundary |
|
Size of a report |
50 MB |
Supported |
The maximum size of a report that can be delivered from SAP. |
Plan for reporting and workflow features
This section describes how the Duet Enterprise 2.0 reporting and workflow features were tested, and provides the test results and recommendations.
Test results and recommendations
The tests outlined in this section measures performance under recommended user load and maximum user load on a Duet Enterprise 2.0 deployment.
With this information, you can better scale deployments based on latency and throughput requirements. It is important to be aware that the specific capacity and performance figures that are presented in this article differ from the figures in real-world environments. The figures presented are intended to provide a starting point for the design of an appropriately scaled environment. After you complete the initial system design, test the configuration to determine whether the system supports the factors in your environment.
Test farm characteristics
This section describes the definitions that the test team used to describe the recommended and maximum capacity loads that were tested and the lab hardware that was used to run the tests.
Green and red zone definitions
For each topology configuration a green zone and red zone user load was determined before throughput tests were run. These configurations are defined in the following table.
| Configuration | Definition |
|---|---|
Recommended (green zone) |
The user load at which the test being run consumes approximately half of the bottlenecking resource. You should expect the green zone throughput to be sustained for long periods of time in real-world deployments. |
Maximum (red zone) |
The user load at which maximum throughput was reached for a topology while latency was at minimum. After this point, throughput typically remained stable and latency increased. You should expect the red zone throughput to be tolerated for a short time on a farm, but it should be avoided whenever possible. |
Lab hardware
The following table lists the specific hardware that was used for the testing.
| Database server | Application server | Front-end web server | |
|---|---|---|---|
RAM |
32 GB |
12 GB |
12 GB |
CPU |
8 Cores (3 GHz) |
4 Cores (3 GHz) |
4 Cores (3 GHz) |
Reporting throughput
The following chart shows the throughput for reporting operations. Throughput is measured by the number of reports processed per second.
Figure Throughput for reporting operations
The following list describes the reports that were used in testing:
30% of the reports are 30 KB.
60% of the reports are 1 MB.
10% of the reports are 10 MB.
The following table summarizes the recommendations of how many front-end web servers that you will need based on the customer size. The recommendations are derived from the reporting throughput test results. The definitions for customer size and usage per user per day are consistent with the definitions used in the SAP capacity planning guide which is available on the SAP Support Portal.
| Customer size | Report characterized by the number of report executions per hour and the report size | Number of WFEs (green zone) | Number of WFEs (red zone) |
|---|---|---|---|
Small |
625 reports (for 1,000 users, 5 report executions per user per day) |
1 |
NA |
Medium |
6,250 reports (for 5,000 users, 10 report executions per user per day) |
1 |
NA |
Large |
93,750 reports (for 50,000 users, 15 report executions per user per day) |
4 |
2 |
Extra large |
187,500 reports (for 100,000 users, 15 report executions per user per day) |
8 |
4 |
Workflow throughput
The following chart shows the throughput for workflow operations. Throughput is measured by the number of workflow tasks pushed per second.
Figure Throughput for workflow operations
The following list describes the work items that were used in testing:
15% of the workflow tasks have 150 KB attachments.
33% of the workflow tasks have three approvers.
The remaining workflow tasks are single-user tasks that have no attachments.
The following table summarizes the recommendations of how many front-end web servers that you will need based on the customer size. The recommendations are derived from the workflow throughput test results. The customer size and usage definitions are consistent with the definitions used in the SAP capacity planning guide which is available on the SAP Support Portal.
| Customer size | Total number of work items to be approved per day | Number of WFEs (green zone) | Number of WFEs (red zone) |
|---|---|---|---|
Small |
1,750 work items (1,000 employees) |
1 |
NA |
Medium |
8,750 work items (5,000 employees) |
1 |
NA |
Large |
87,500 work items (50,000 employees) |
1 |
NA |
Extra large |
175,500 work items (100,000 employees) |
1 |
NA |
See also
Overview of Duet Enterprise for SharePoint and SAP Server 2.0