System Sizing Spreadsheet

EMC | Documentum 6.5(covers: Webtop, Content Server, Task Space and High Volume Server)

EMC Proprietary and Confidential

Documentum and the Corporate Logo are trademarks or registered trademarks of EMC Corporation in the United Statesand throughout the world. All other company and product names are used for identification purposes only and may betrademarks of their respective owners.

Last Update: 3/24/2010WARNING: Information in this tool is likely out-of-date. Please obtain a new version from Documentum.

This Sizing Spreadsheet is for Documentum Version 6.5 only.

180For assitance with the sizing tool, please email cma_sizing_help@emc.com

Copyright © 1994-2010. EMC Corporation.  All Rights Reserved.

Documentum and the Corporate Logo are trademarks or registered trademarks of EMC Corporation in the United Statesand throughout the world. All other company and product names are used for identification purposes only and may be

WARNING: Information in this tool is likely out-of-date. Please obtain a new version from Documentum.

This Sizing Spreadsheet is for Documentum Version 6.5 only.

EMC 6801 Koll Center Parkway Pleasanton, CA 94566 925-600-6800

All other company and product names are used for identification purposes onlyand may be trademarks of their respective owners.

Copyright © 1994-2010. EMC Corporation.  All Rights Reserved.

Documentum and the Corporate Logo are trademarks or registered trademarks of EMC Corporation in the United States and throughout the world. All other company and product names are used for identification purposes only and may be trademarks of their respective owners.

The information in this document is subject to change without notice and for internal use only. No part of this document may be reproduced, stored, or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of EMC Corporation. EMC Corporation assumes no liability for any damages incurred, directly or indirectly, from any errors, omissions, or discrepancies in the information contained in this document.

All information in this document is provided “AS IS”, NO WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE MADE REGARDING THE INFORMATION CONTAINED IN THIS DOCUMENT.

This spreadsheet automatically provides estimates of a customer's hardware resource needs based on user and hardware profiles provided by the customer. Use this spreadsheet as an aid when you are working with a customer to size a Documentum deployment. The figure below illustrates the spreadsheet's use.

It is less useful for deployments that are highly customized or are not primarily made up of the Edition software.

and analysis. Most of the information that underpins this sheet is summarized in the DocumentumSystem Sizing guide. Additional detail can be found in the detailed benchmark reports.

Please find updated Sizing Tools and other Sizing materials at the PowerLink and Developer Websites.

Search under : Home > Support > Technical Documentation and Advisories > Software ~ D ~ Documentation > Documentum System > Systems Sizing

The spreadsheet focuses primarily on sizing deployments of the standard Documentum Editions.

The hardware resource estimates given in the spreadsheet are derived from Documentum performance benchmarks

EMC Powerlink

Enter Workload information on "Customer Input Page"

Enter Document information on "Customer Input Page"

Talk with hardware vendor and enter hardware profile on "Customer Input Page"

Inspect Estimated hardware usage from "Output Summary

Page"

Check with hardware budget and then adjust workload &

document information accordingly

Budget for hardware and software purchases

start

needs based on user and hardware profiles provided by the customer. Use this spreadsheet as an aid when you are working with a customer to size a Documentum deployment. The figure below illustrates the spreadsheet's use.

Please find updated Sizing Tools and other Sizing materials at the PowerLink and Developer Websites.

Search under : Home > Support > Technical Documentation and Advisories > Software ~ D ~ Documentation > Documentum System > Systems Sizing

from Documentum performance benchmarks

What's New: 1. Updated D6.5 Numbers 2. Corrected errors in the sheet

1. Spreadsheet output should be considered suspect at either an extremely low number of users or a very large number of users. Please review large user scenarios with your account team (and the performance team as needed). 2. If you need assistance with the Sizing tool you may contact your Account Manager, Professional Services, or you may send an email to cma_sizing_help@emc.com. 3. CPU, Memory and I/O estimates are based on our own workload testing. Actual customer workloads (and usage) could differ from this. 4. Geographic location and separate docbases could imply additional needed servers. 5. This tool assumes that most other machine improvements go hand-in-hand with Mhz improvements. 100% more users can be served on an 800 Mhz system vs. a 400 Mhz system. 6. Original benchmarks where performed on 1.2 GHz Sun UltraSparc III processor. 7. This tool assumes that UNIX, including Linux, and NT machines can serve the same number of users with equal processors and Mhz.

detailed benchmark reports for more information on the actual workloads.

14. The database memory requirements do not accurately account for concurrent user memory needs. If in doubt add more memory for the database. Also, some recommendations may exceed what a database could support in a single instance. In those cases it will be necessary to decrease the memory for the RDBMS by reducing the buffer cache.

17. The deployment section of the Output Summary now rounds the number of cpu's per machine up to an even number if greater than 1.18. The deployment section of the Output Summary no longer reports number of cpu's for the Index Server/Agent if the number of machines is 0.19. Removed Beta notice.

21. Added missing MTS cpu output.22. Added SQL Server 2005 as a database choice.23. Updated TaskSpace calculations.24. Added multi-core support

Limitations, known bugs, and other notes [updated]

8. This tool does not take into account the usage of Vmware. 9. This tool does not take into account temp areas, program installation areas, and operating system areas for disk space calculations.10. This tool does not take into account varying bandwidths for client PC to server interactions.11. This tool does not take into account varying PC machine Mhz. The focus is on server hardware not client hardware.12. The workloads in this tool did not include any large batch operation that could impact resource consumption. See

13. The hardware resource estimate does not include network bandwidth estimates or estimates for hardware load balancers.

15. Spreadsheet does not cover any Documentum Distributed feature (Replication, Content servers, Branch Office Caching Services, etc.).16. This release does not factor in throughput or space needs of various hardware RAID options.

20. Fixed BPS Calculation displays. Input cells: C70 and Output cells C19, B19, B45, B77

1. Spreadsheet output should be considered suspect at either an extremely low number of users or a very large number of users.

2. If you need assistance with the Sizing tool you may contact your Account Manager, Professional Services, or you may send an email to cma_sizing_help@emc.com. 3. CPU, Memory and I/O estimates are based on our own workload testing. Actual customer workloads (and usage) could differ from this.

5. This tool assumes that most other machine improvements go hand-in-hand with Mhz improvements. 100% more users can be served

7. This tool assumes that UNIX, including Linux, and NT machines can serve the same number of users with equal processors and Mhz.

database could support in a single instance. In those cases it will be necessary to decrease the memory for the RDBMS

17. The deployment section of the Output Summary now rounds the number of cpu's per machine up to an even number if greater than 1.18. The deployment section of the Output Summary no longer reports number of cpu's for the Index Server/Agent if the number of machines is 0.

take into account temp areas, program installation areas, and operating system areas for disk space calculations.

not client hardware. include any large batch operation that could impact resource consumption. See

include network bandwidth estimates or estimates for hardware load balancers.

cover any Documentum Distributed feature (Replication, Content servers, Branch Office Caching Services, etc.).

EMC | Documentum Sizing Input Page WARNING: Information in this tool is likely out-of-date.

Step #1: Enter User/Workload Profile Please obtain a new version from Documentum.

User Profile Webtop 6.5 TaskSpace 6.5Heavy Users 200 N/ALight Users 500 0%Heavy Users Active 100% 0%%Light Users Active 10% 10%Heavy Users/Busy hour 200 0Light users/Busy hour 50 0

250 0Estimated % Growth of Users Per Year 50% 0%Level of Customization Light NoneWorkflow Intensive No Yes

Note: While the WebTop and TaskSpace calculations are fine for estimating total server hardware, they should not be used to compare the 'cost' of using Webtop vs. TaskSpace. The workloads for each are significantly different. This difference has been accounted for in the hardware sizing, but does not represent a fair comparison between Webtop and TaskSpace.

Workload-Specific Criteria WDK/Webtop based ApplicationsContent Server Session Pooling EnabledNumber of custom types 50 Extended HTTP TimeoutNumber of CS Instances per machine 1 Clustered App Server

Peak Fulltext Queries per min

no

Step #2: Enter Document Profile Content Loading CPU InputContent Profile Loading days per yearNum of Original Source Documents: Yr 1 9,000,000 Num. of Docs/DayEstimated Average Size (kbytes) 1000 Content Input Window (hrs)Avg. Versions per Document 1 Num. AutoWF Tasks per DocAverage Additional Renditions 0 Average Size (Kb)

Custom Attribute size per Doc (kbytes) 1 Renditioning PriorityNumber of Custom Attributes 15 Full Text Indexing

Regular Objects

Document Sizes(kb):

Average Size (KB) % of AllFormat/Input TypeWord 1,000 5,400,000 60%PPT 0 0 0%PDF 1,000 3,600,000 40%HTML/Web Pages 0 0 0%XML/text 0 0 0%Images 0 0 0%Contentless 0 0 0%MPEG 0 0 0%

Total 2,000 9,000,000 100%Weighted Average 1,000

LightWeight Objects (Requires High Volume Server)

Total Users/Busy hour

Document or MediaTransformation Services?

Number of Source Docs in First Year

Document Sizes(kb): Parent

Input TypeExample 50,000 1000 25

Step #3: Enter Platform Profile Information Years of Coverage for Hardware 5High Availability Needs disaster recoveryDatabase Server Type OracleJVM version 1.6

CPU type MHz

Web-tier machines Intel_IA64 3000 2Content Server machines Intel_IA64 3000 2Index Agent machines Intel_IA32 2400 2Index Server machines Intel_IA32 2400 2RDBMS machines Intel_IA64 3000 N/ABPS Server machines Intel_IA32 2400 2Site Caching Services Target machines Intel_IA32 2400 2Document Transformation machines Intel_IA32 2400 2PDF Aqua Server machines Intel_IA32 2400 2Media Transformation Servers Intel_IA32 2400 2

EMC Proprietary and Confidential

Number of Source Docs in First Year

Number of New Docs

Per YearAvgerage Object

Size (KB)

Note: This area is useful in working "WHAT IF?" scenarios with your hardware vendor

Physical CPUs per server

WARNING: Information in this tool is likely out-of-date.

Please obtain a new version from Documentum.

WDK/Webtop based Applications BPMSession Pooling Enabled Yes Peak Manual Activities per min 0Extended HTTP Timeout No Automatic Activities per hour 0Clustered App Server No BPS messages per hour 0Peak Fulltext Queries per min 10

Content Loading CPU InputLoading days per year 260

30Content Input Window (hrs) 24Num. AutoWF Tasks per Doc 0Average Size (Kb) 2000

NoneRenditioning Priority Low PriorityFull Text Indexing Immediate

No 800,000 0 30% 1 Yes 0No - 0 50% 1 Yes 0No 1,200,000 0 0% 1 Yes 0No - 0 40% 1 Yes 0No - 0 0% 1 Yes 0No - 0 20% 1 No 0No - 0 0% 1 No 0No - 0 15% 1 No 00 2,000,000

0 15% 1.0

** Do not include these documents in the profile below.

Document or MediaTransformation Services?

** This fulltext flag is for all workload profile calculations.

Request Media Transformation?

Number of New DocsPer Year

Avg. # of Add'l Rend.

Avg. Rend. Size(% of Orig)

Average # of Versions

Content can be FT Indexed

Avg Fixml size KB (if

known)

Child

% Materalized1,000 100 25 20% <--- This row will NOT be included

Cores per CPU Planned # of servers disk I/Onon-HA HA capacity

2 1 22 1 2 used only to detect if the planned number of servers 2 1 2 you intend to purchase will not meet the capacity2 1 2 350 demand.2 1 22 1 22 1 22 1 22 1 22 1 2

EMC Proprietary and Confidential

Number of Children / Parent

Avgerage Content Size

(KB)

Avgerage Object Size

(KB)

This area is useful in working "WHAT IF?" scenarios with your hardware vendor

Note: The "planned number of servers" will be

EMC | Documentum System Sizing Output Page

User Profile SummaryUser population after 5 years 3,544Users/busy hour after 5 years 1,266Number of Documents from all sources after 5 years

WARNING: Information in this tool is likely out-of-date. Obtain an updated version

Estimated Hardware Resource SummaryOutput CPUs Cores 2 Memory (MB)

Content Server 2 2 13,824 16,677,734 Index Agent/Server 4 6 [ alt. 3.7 5,272 14,367,116 WDK/App Server (Web) 2 2 7,168 RDBMS Server 2 2 2,048 50,768 10Total for Servers 10 12 28,312 31,095,618

Document Transformation Svr 0 0 Note: These estimates are NOT adjusted for High Availability BPS Server 0 0Media Transformation Svr 0 0

Hardware Deployment Options (note: Not Adjusted for HA needs)

Option #1 # of machines CPUs/machine Cores/CPUHost-based (Web + Content Serv. + FT + DB) 1 10 2

Option #2Web Tier Server separate 1 2 2Content Server/FT Index subsystem combined 1 6 2RDBMS separate 1 2 2

Option #3Web Tier separate 1 2 2Content Server separate 1 2 2Index Agent 1 2 2Index Server (Full Text Index) 1 2 2RDBMS separate 1 2 2

Other ServersDocument Transformation Service PCs 0 2 2BPS Servers 0 2 2Media Transformation Svr 0 2 2

Full Text NotesNote: the calculated full text Disk I/O load (402 I/O's per sec) exceeds the entered capacity (350 I/O's per sec)WARNING: The total num of docs or size exceeds what can be handled by a single Index Server Search Node.

17,039,000 17,039,000

sourcesource + versions + rend.

DiskSpace (MB)

Note: The large full text partition merge could take as long as 9312 min, this may impact save-to-search latency(c) 2007 EMC Inc EMC Proprietary and Confidential

Adjustments for High Availability

Desired High Availability Option disaster recovery

Option #1 # of machines CPUs/machine Cores/machineHost-based (Web + Content Serv. + RDBMS) 2 10 2

Option #2Web Tier Server separate 2 2 2Content Server/FT Index Subsystem combined 2 6 2RDBMS separate 2 2 2

Option #3Web Tier separate 2 2 2Content Server separate 2 2 2Index Agent / Index Server (Fulltext) 2 2 2Index Server (Full Text Index) 2 2 2RDBMS separate 2 2 2

Other ServersDocument Transformation Service PCs 0 2 2BPS Servers 0 2 2Media Transformation Svr 0 2 2

(c) 2007 EMC Inc EMC Proprietary and Confidential

Important Notes1. These are estimates only. Actual system usage could vary. Please review README sheet.

Note: Fulltext HA configurations to be supported starting in 5.3 SP1

Please contact PMO for large volume of users

2. The disk estimates (space and spindles) do not take into account any RAID overhead.3. The disk estimates (space and spindles) do not take into account work areas, install space, or OS files4. The memory estimates do not account for OS needs or needs by other applications

EMC Proprietary and Confidential Rev:40261

WARNING: Information in this tool is likely out-of-date. Obtain an updated version

10403133143

690

Note: These estimates are NOT adjusted for High Availability

Note: the calculated full text Disk I/O load (402 I/O's per sec) exceeds the entered capacity (350 I/O's per sec)WARNING: The total num of docs or size exceeds what can be handled by a single Index Server Search Node.

source + versions + rend.

Est. DiskIOs/sec

Note: The large full text partition merge could take as long as 9312 min, this may impact save-to-search latency

See note belowSee note below

take into account work areas, install space, or OS files

Bulk Load Calculation PageWarning: DON'T ALTER ANY VALUES ON THIS PAGE

Num. of Docs/Day 30 cpu secs per auto-wf task # of docs CPU min/opContent Input Window (hrs) 24 Oracle 39 48.750 0.2 0 103982 0.000468831docs/day (alt 7,692 CS 60 75.000 0.08 0 103982 0.000721279

dmbasic 11.13 13.913 10000 0.00139125

Oracle eCS LoaderCPU minutes needed for batch 0.014064934 0.02163836 0.0417375batch window CPU mins avail 1440 1440 1440number of CPUs required 1 1 1

eCS RDBMSbatch window (seconds) 86400 86400 25%docs per second 0.000347222 0.000347222disk I/Os per doc 3.260869565 2.536231884required disk I/O per sec 0.001132246 0.000880636disk I/Os per sec per spindle 40 40

disk I/Os per sec 0.001132246 0.000880636

Chase's old formula for database disk io = (50*60*21)/10000Chase's old formula for content server disk io = (337*60*21)/10000

52 loaders - measured CPU/Min to store 103982 docs

increase due to steady state deletion

# of auto workflow tasks/doc

% increase due to steady state deletion