Problem solve Get help with specific problems with your technologies, process and projects.

Using Performance Optimizer

Exchange Tip: Using Performance Optimizer

Using Performance Optimizer

There are some helpful functions that administrators may neglect to run on a regular basis. One of them is Exchange Server's Performance Optimizer. This tip, excerpted from InformIT, notes when Performance Optimizer should be run and what kind of errors you can see if you do not run it regularly.

Performance Optimizer
Aside from message delivery events, you should also be aware of events that prompt you to run the Performance Optimizer. You probably remember that after you installed Exchange Server, you were prompted to run the Performance Optimizer. Hopefully you did so at the time and continue to use the Performance Optimizer to analyze your system resources and configure system variables appropriately, based on information you provide about your current messaging environment.

Ideally, the Performance Optimizer should be run whenever any of the following is true:

  • An Exchange server's functions have changed
  • Users have been added to the server
  • Users have been added to the organization
  • Resources (such as memory) have been added to the server

[You can get the following error if] the administrator elected to not run the Performance Optimizer after installation [or if] the Performance Optimizer was not re-run regularly with the expansion of the messaging system:

"The total number of threads (XX) configured for the Information Store is too low. Assuming YY threads."

The value for XX is smaller than the value for YY, indicating that Exchange decided for itself in real-time that it could not operate sufficiently under the current conditions. This error indicates that you need to re-run the Performance Optimizer.

More often than not, companies that get this message in the event viewer tend to ignore it because it is not a STOP error and Exchange appears to be self-optimizing. This is a bad practice; although Exchange is attempting to repair itself, it is by no means optimizing itself on the fly. [You can also get] this error during upgrades in which, occasionally, the Exchange server will fail to start correctly as a result of the problem. If this happens to you, and you are unable to run the Performance Optimizer, you can try editing the Registry value HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices MSexchangeISParametersSystem.

Change the value for Minimum Threads to a larger number. Remember to always back up your Registry before editing anything!

To read more of this article go to Registration is required, but it's free.

For more information on Exchange Server check out this book in the TechTarget eMarketPlace:

Microsoft Exchange 2000 Server Resource Kit
by MS Press
This powerhouse reference packs 900 pages of detailed technical drill-down covering Exchange 2000 Server architecture, deployment, installation, administration, backup and recovery, security, troubleshooting, performance optimization, and application development.

This was last published in November 2000

Dig Deeper on Microsoft Exchange Server Monitoring and Logging

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.