New performance best practices white paper

robert.m.hoover — Mon, 26 Oct 2009 16:20:00 GMT

Performance and capacity planning best practices

This download contains two white papers:

Performance testing white paper
Performance and capacity planning best practices white paper

Performance testing white paper

This white paper contains a description of an actual performance testing lab for Microsoft Office Project Server 2007.

The first chapter (“Running a Project Server 2007 Performance Test Lab”), describes how to run performance tests against a Office Project Server 2007 deployment by using Visual Studio Team System 2008 and a set of community-based tools built for the purpose.

The second chapter (“Test Environment”), documents the specifics of the lab environment that was used for the tests we ran for collecting data for this white paper.

The third chapter (“Test Results”), describes in detail the test scenarios that were conducted, and it summarizes the data collected for every scenario.

The paper is available from the Microsoft Download Center.

Download size: 4 MB

Performance and capacity planning best practices white paper

The purpose of this guide is to extend the Microsoft Office Project Server 2007 Performance Testing Lab white paper by providing best practices and recommendations.

This paper examines a wide array of system objects, including:

Platform-related objects — including the farm, shared service providers, application pools, web applications, databases, disks, network, memory, CPU, logs, and performance counters
Data-related objects — including projects, tasks, assignments, resources, custom fields, and security
User-related objects — including localization, workloads, queue job processor threads, and interface feeds

For each system object, the following information is provided:

Definition — The definition of the object
Guidelines for acceptable performance — The best practices and supporting statements
Calculation factors — The performance and scalability calculations to support the best practices
Scope of impact — A list of objects affected in the system when best practices are not implemented

Microsoft Project Server 2007 IT Professional TechNet Webcast Series

robert.m.hoover — Wed, 24 Sep 2008 23:30:00 GMT

I just wanted to pass on word that starting October 1^st, 2008, Michael Jordan (Lead Architect – MCS EPM Global Practice | WW COE for EPM) will present a series of Project Server 2007 webcast on TechNet targeted at IT Professionals.

These 60 minutes webcasts will present in details key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007 specifically:

· Solution Overview and System Elements

· Solution Elements and Data Flow

· Workload Scenarios and Reference Architecture

· Network Communication

· Server Administration

· Maintenance and Monitoring

· Deployment into a SharePoint Server Intranet Farm

· Disaster Recovery

· Virtualization

You need to register for the free of charge webcast by clicking the link; then you get emailed a link to sign on and participate in the web cast on its date and time (please note only the first two webcast are available for registration at this stage).

Each TechNet webcast is recorded for later viewing which should be through the same registration URL.

For a listing of all EPM webcasts on TechNet check the following: http://www.microsoft.com/events/series/epm.aspx

Webcast Title

Abstract

Date

Microsoft Office Project Server 2007 - Solution Overview and System Elements

In this webcast, we introduce the Microsoft Office Project Server 2007 solution and the main product components. We describe key concepts such as high availability and scalability, which should be taken into account when planning and deploying Project Server 2007. This introductory webcast is part of a webcast series targeted at IT professionals. In the series, we present in detail key aspects to consider when you evaluate, plan, deploy, and operate Project Server 2007. We discuss the main considerations when planning for high-availability deployments—when to scale up and out, points of failure, and software/hardware boundaries.

Wednesday, October 1, 2008