Plan a Project Server 2013 performance test lab
Applies to: Project Server 2013
Topic Last Modified: 2013-12-18
Summary: Planning is the first and most important phase of every complex task for Project Server 2013, and performance testing is no exception to this rule.
For specific information about how to plan your Project Server 2013 installation, see Plan for Project Server 2013.
Before setting up the environment and running tests, you should thoroughly plan for all the aspects of what you will do. The following table summarizes some key points that you have to plan for.
Aspects of a Project Server 2013 performance test lab to plan for
Your lab configuration should be as close as possible to your existing or target production environment. For future reference, make sure that you keep track of the details of your hardware configuration before completing the lab.
Plan for installing the latest fixes available for every software component in your lab. If you plan to run the lab for a long time (one month or more), you should also plan to update the systems when it is necessary with the latest security fixes. If you do not strictly have to change the software configuration of your systems, you should avoid changes during the lab timeframe, in order to maintain data comparability across different test runs performed at different times.
Your lab should have enough storage space to store:
Your lab environment should be put on an isolated network, in order to minimize the effect of extraneous network activities on your tests. One computer in the lab is usually configured as a bridge for remote access to the lab from the corporate network.
Because you have to simulate users who are accessing your lab environment, and you have to know the passwords for each simulated user, you must plan for the Directory Services to be used. You should plan for a dedicated organizational unit (OU) in an existing Active Directory directory service domain for managing the test user accounts, or for a dedicated Active Directory domain for your lab environment.
Based on your overall goals for the performance lab, your test scenarios must be planned carefully. Consider the following elements for every test scenario:
Putting together all the test scenarios that you will perform, plan for your overall data population strategy by identifying the minimum number of data profiles that you will need for your tests. Data profiles typically include the following elements:
You should plan for an appropriate naming convention for all the test entities (users, projects, tasks, and so on).
Run a Project Server 2013 performance test lab
Key performance metrics for Project Server 2013
Set up the test environment for Project Server 2013
Test user-initiated write operations that involve Project Server 2013
Test user-initiated operations that involve Project Professional 2013
Test background operations in Project Server 2013
Extract and analyze test data in Project Server 2013