Sunday, March 20, 2005

Webpart overkill?

I've spent last week searching through logs for a clue as to why a Portal has been so slow to respond to page requests; sometimes as long as 70+ seconds...

We haven't discovered what causes the delay yet, but what we have discovered is that the worker process memory usage gradually grows to the maximum 800 MB. This is when the response-time issue start to happen. This usually takes place during the day when Portal usage is expected to be high.

So far we've been able to create a temporary workaround by adding a third web frontend to the Sharepoint Portal Server farm. The cause of the memory fillup followed by the large response times is as yet unknown.

Moral to this (continuing) story:

If there are no obvious signs (CPU/Memory/IO) as to why your Portal is reacting so slow to user requests and you want to find the cause, there are three pieces of the puzzle you want to have to be able to do some serious troubleshooting:
  1. User statistics. Think IIS logging.
    Why? You want to be able to compare usage to any other statistics gathered from your systems.
  2. System Statistics. This can be anything from ASP.NET counters to network usage to SQL tracing. Basically, how is your farm/infrastructure behaving?
  3. Webpart architecture. This is especially important if there has been some serious webppart programming going on in your Portal environment. Even more so if external datasources are accessed. Think web services, databases etc.

Bottom line

When webparts are introduced in your Portal System they will alter the behaviour of your Portal farm. Don't be caught off-guard.


Comments: Post a Comment

Links to this post:

Create a Link

<< Home

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]