Timing Estimation

The following timing numbers are only an approximation for P6 EPPM. The actual numbers for your deployment depend on the data structure and the hardware used.

Note: For planning and sizing purposes, Primavera Unifier databases are considered "small".

Initial ETL

 

Number of Objects

 

Small

Medium

Large

Projects

200

1,000

15,000

Activities

100,000

500,000

4,000,000

Resources

5,000

5,000

5,000

Resource Assignments

30,000

100,000

2,000,000

Codes Mapped

1

1

200

UDFs Mapped

0

0

200

Project with History (percentage of total)*

5.00%

5.00%

50.00%

Backlog of ETL runs

--

--

--

STAR_DATx cumulative size**

3.5 GB

8 GB

90 GB

STAR_HSTx cumulative size**

< 1 GB

< 1 GB

< 1 GB

Full ETL Approximate completion time

< 1 hr

< 1 hr

~ 7 hrs

LOAD_PLAN_INITIAL_LOAD

< 1hr

< 1 hr

5 hrs

Incremental ETL - 2 months of history and Slowly Changing Dimensions

 

Number of Objects

 

Small

Medium

Large

Projects

200

1,000

15,000

Activities

100,000

500,000

4,000,000

Resources

5,000

5,000

5,000

Resource Assignments

30,000

100,000

2,000,000

Codes Mapped

1

1

200

UDFs Mapped

0

0

200

Project with History (percentage of total)*

5.00%

5.00%

50.00%

Backlog of ETL runs

60 days

60 days

60 days

STAR_DATx cumulative size

8 GB

17 GB

255 GB

STAR_HSTx cumulative size

< 1 GB

< 1 GB

60 GB

Full ETL Approximate completion time

~ 2 hrs

~ 3 hrs

~ 11 hours

LOAD_PLAN_DAILY

< 1 hr

< 2 hrs

< 4 hrs

*In performance runs, history level is all Activity Levels. This is a worst case scenario.

**Oracle data files: depending on how you manage your tablespace, you can have a different number of data files.

Related Topics

Planning Revisited

Factors Affecting ETL Runtime



Legal Notices | Your Privacy Rights
Copyright © 1999, 2020

Last Published Monday, December 14, 2020