Microsoft Sharepoint Products and Technologies Resource Kit eBook

266 Part III: Planning and Deployment
■ Do not run logging on this server
■ Log critical events only
■ Log informational events and critical events
■ Log all tracing information
You can choose one of these options for each computer running SharePoint
Portal Server. You can also configure a separate log that keeps track of information
for a specific service. The SharePoint Portal Server services that provide logging
capabilities are as follows:
■ WWW Worker Process (w3wp.exe)
■ Administration Service (spsadmin.exe)
■ Search Service (spssearch.exe)
■ Backup and Restore (spsbackup.exe)
■ Notification Service (spsNotificationService.exe)
■ Single Sign-On Service (ssosrv.exe)
Monitoring Custom Web Parts
Most customers customize the accelerator portal by developing new Web Parts, integrating
with other applications, or using third-party Web Parts. Before adding a Web
Part to the production portal, you should evaluate the impact of the load generated
by new Web Parts.
Most companies have a separate development environment for this purpose,
and some have staging environments that closely mimic the production portal configuration,
which provides a more realistic picture of the impact of adding new Web
Parts. In any case, you should thoroughly debug and test any custom Web Part and
have a good understanding of the possible load that a new Web Part will generate
in your accelerator portal.
Table 10-15 details the information you can use to compare the performance
baseline of your portal with custom Web Parts against the results of your portal
when it did not include the Web Parts. You can then determine the additional load
and possible impact on other performance counters. These counters are available
through Windows Server 2003 System Monitor.