eG Monitoring
 

Measures reported by P6EPPMUsersTest

The Oracle Primavera allow for a wide variety of user roles, each one with specific privileges and activity levels. The central Primavera server or cluster responds to the requests to all logged in users. The number of users logged and kind of activity performed by them directly affects the overall system performance. It is important for the administrators to know, at any given time, what is the number of logged in concurrent users, what is the activity level of user which is reflected by user role, and what is the method through which users are logged on, e.g. whether the users are logged on through Power client, API or web interface.

This test measures the number of various different kind of users logged and provides administrators with valuable insights about current and future performance issues. On the basis of these statistics administrators can plan adding more capacity to Primavera cluster if usage is high.

Outputs of the test: One set of results for P6 EPPM Server

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
loggedInUsers Indicates the total number of logged in users on P6 EPPM server. Number

The number of logged in concurrent users directly affect the performance of the server. Administrators should monitor this measure for extended period to understand the user login trends and plan the server capacity accordingly.
uniqueTotalLoginsUsers This is the total historic count of unique P6 EPPM users that have logged into the system. This count will never exceed the total number of users in the user dictionary. Number

This is the maximum number of users that can login in the system that can system.
p6AnalyticsUsers Indicates the number of analytics users session which are currently active. Number

Analytics users tend to consume most compute resources. In case the number of analytics resources are high at any given point of time, administrators needs to plan system capacity accordingly.
apiUsers Indicates the number of users who are connected through P6 EPPM API. Number

API users can perform mix activity
webServicesUsers Indicates the number of users who are accessing through P6 EPPM Web Services. Number

 
powerClientUsers Indicates the number of users who are connected through Power Client. Number

Power client allows enhanced functionality and allows users to carry out heavy operations like project setup, changing the structure, loading date etc. High number of active power client users can degrade the performance of the system.
resourcesUsers Indicates the number of users who have access to EPPM Resource Access field. Number

 
timesheetUsers Indicates the number of users who have access to timesheet tab in P6 Team Member web. Number

Timesheet users are mostly view only users who look for timeshet reports, administrators can expect a lot of database queries running if number of timesheet users is high.
projectsUsers Indicates the number of users who have access to Projects section in P6 EPPM. Number

 
portfoliosUsers Indicates the number of users who have access to Portfolio section in P6 EPPM. Number

 
eReportsUsers Indicates the number of logged in users who have access to run Enterprise reports. Number

Running enterprise reports can be a heavy operation and if the users are running the reports in real time, it could really put a lot of load on the system. Ideally very few users should have access to run enterprise reports.
teamMemberUsers Indicates the number of logged in users who have access to P6 EPPM Team Members module. Number

 
teamMemberIFUsers Indicates the number of logged in users who have access to P6 EPPM Team Members Interface module. Number

 
profileUsers Indicates the number of logged in users who have access to configure and manage security profiles of other users. Number

This mostly include operations like adding new user and configuring roles for them. These are mostly light weight operations and don't require much server resources.