Suppose your users complain that the website takes a long time to load once they login. It's problem solving question. Let's break it down into the areas where the problem might be:
1. Server scripts
2. Database
3. Browser
4. Client scripts
5. Actual server
Lets address each area:
1. Server scripts
Server side code has some faults. What if there is an long loop of inefficient code?
2. Database
There might be a lot of concurrent users on the application and which leads to a lot of database reads and writes. There are several ways to find out how much time that it takes to execute a particular query.
2. Database
There might be a lot of concurrent users on the application and which leads to a lot of database reads and writes. There are several ways to find out how much time that it takes to execute a particular query.
3. Browser.
Our website wasn't loading on IE either since we had not published the P3P policy.
Our website wasn't loading on IE either since we had not published the P3P policy.
4. Client scripts.
Errors in JavaScript.
5. Server issues.
Less RAM? Too many programs or users running concurrently may be one of the reason why the server takes a long time to respond. Why don't you check if the website loads properly at time of when there are few users accessing the system?
Errors in JavaScript.
5. Server issues.
Less RAM? Too many programs or users running concurrently may be one of the reason why the server takes a long time to respond. Why don't you check if the website loads properly at time of when there are few users accessing the system?
By the way, I came across this great post at Kissmetrics.
No comments:
Post a Comment