OWSTIMER ! Memory Leakage

Often the OWSTIMER.EXE process will allocate significant amounts of memory . As more and more memory is allocated to OWSTIMER, less is available for other processes, most notably the Internet Information Server (IIS) web service (W3SVC). If IIS does not have sufficient memory, a serious performance penalty will result. The workaround for this memory leakage to stop and then start the OWSTIMER process. This can be accomplished using the built-in Services application (under Administrative Programs in the Start menu) or via the command line. (The command-line entry is “net stop WSSTimerV3“.) In a large farm deployment, the service will be running on many Web Front Ends ( WFE’s) so the workaround must be performed on all of them.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s