16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

226 Part III: Planning <strong>and</strong> Deployment<br />

that might be of interest to you during the load simulation. You can monitor<br />

counters on remote servers, but this is not recommended during stress testing, as the<br />

resources required to send the performance data to the monitoring client might<br />

affect the test results. For more information on performance monitoring <strong>and</strong> exactly<br />

what to monitor with respect to SharePoint Portal Server, please refer to Chapter 10.<br />

Scenarios for Load Stress Testing<br />

One of the most important tasks before performing any stress tests is to underst<strong>and</strong><br />

what the different scenarios can be. These scenarios could be written down <strong>and</strong><br />

then ordered by weight. It makes sense to test these scenarios, as they represent<br />

most common tasks the users will perform <strong>and</strong> therefore should result in the fastest<br />

response time possible. There are some tasks for which users simply expect a fast<br />

response time, while there are others where they can accept slower response<br />

times—for example, administrative tasks.<br />

Performance scripts can be created to mimic anticipated load on the portal site.<br />

The scenarios that follow represent the most commonly occurring scenarios, but if<br />

your scenario differs, feel free to adjust according to your customized usage profile.<br />

The Portal Home<br />

SharePoint Portal Server allows you to create several portal sites. These are basically<br />

the main places for information in an enterprise implementation <strong>and</strong> will be one of<br />

the most requested locations in the intranet. It is important that at least the Home<br />

page opens up in a very fast manner. Normally, the corporate portal site will receive<br />

20 percent of the total farm traffic, <strong>and</strong> the Home page of the corporate portal site<br />

will receive a significant amount of that traffic.<br />

My Site<br />

Personalization was one of the biggest dem<strong>and</strong>s of the users of the previous version<br />

of SharePoint Portal Server. In SharePoint Portal Server 2003, every user can go to<br />

his personal site by clicking My Site in the upper right corner. There is a personal<br />

<strong>and</strong> shared view for each user. The user can decide between the shared <strong>and</strong> personal<br />

view of the site <strong>and</strong> do some modifications. As most of the time people will<br />

access mainly their own sites, we will focus on the Personal View page <strong>and</strong> not on<br />

the Shared View.<br />

The Shared View should be tested if you plan on using the corporate portal site<br />

as a corporate directory. Because the Shared View of the My Site, combined with<br />

user profiles, provides a very nice corporate directory, some organizations will make<br />

use of this feature. In this instance, you should make public My Site views a low<br />

percentage of testing because the public.aspx is one of the most expensive pages to<br />

render. If you do not plan on using Shared Views as a corporate directory, it is not<br />

necessary to include the Shared Views in your stress-testing plans.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!