Slow Web App - Suggestions?

I have an application that is accessed over the web. Opening the database is painfully slow. The main view consists of about 17,000 documents. Each user has about 200 documents that pertain to them. Originally I had reader fields but I just removed those hoping for better performance. No such luck.

I’m now using a single category view based on the user’s name to pull up just the users relevant documents. However, it’s still very slow. The view selection criteria is very simple. The view columns contain HTML to display various fields. Nothing overly complex.

Is there anything else I can do to improve performance? The way it is now it is basically unusable. The application will often time out before displaying the view.

The server is also very overworked which isn’t helping, but any pointers would be welcome.

Subject: Slow Web App - Suggestions?

Ghost,

There are so many factors to consider when troubleshooting performance. There are a few articles on DevNetwork that you could read for tips.

If the server is just bogged down, then of course there isn’t much your app can do to help, aside from not worsening the situation. But in terms of analyzing the performance problems as they now exist, I usually start with agent manager and the update task. Again, see those articles for logging tips.

regards,

raphael

Subject: Poor man performance tuning

When I run into this

  1. Look at the columns and view selection for time functions

  2. If the data does not change that much I set the view indexes to update as little as possible. This makes a huge difference if you can afford to do it.

  3. If that does not work I go to the performance articles