Suppose that remote users are connecting to your application via a web browser o

Question

Suppose that remote users are connecting to your application via a web browser over the Internet. Some users are complaining of performance bottlenecks, while the majority of users are not experiencing the problem. The correct approach to diagnosing and resolving this issue would be to:

Select one of the following:

- Begin by describing and simulating all facets of the user experience, especially connectivity components. This may reveal what the troubled users have in common, such as external issues such as proxy, firewall, and network bottlenecks.
- Focus on the application rather than the database or external factors. Since only a portion of the users are experiencing problems, database issues are ruled out, as database issues always impact all users equally. Similarly, external issues cannot be a factor, because such factors would result in the users not being able to connect to the system in the first place.
- Begin with a full analysis of the database system, beginning with performance logs, such as those that document slow/long-running queries. Since application developers can tell you from experience that 95% of performance problems reside in the database, it is wise to play the odds and look at the biggest offender, first.
- Ignore it. In any large, database-driven, web-delivered application, there are bound to be a number of users at any given time that are having problems with misconfiguration of the client computer, slow internet connections, firewall problems, or proxy problems. These are external problems beyond your control as a database administrator, and can simply be ignored.

Suppose that remote users are connecting to your application via a web browser over the Internet. Some users are complaining of performance bottlenecks, while the majority of users are not experiencing the problem. The correct approach to diagnosing and resolving this issue would be to:

Select one of the following:

Explanation / Answer

I would gor for the approach "Begin with a full analysis of the database system, beginning with performance logs, such as those that document slow/long-running queries. Since application developers can tell you from experience that 95% of performance problems reside in the database, it is wise to play the odds and look at the biggest offender, first."

Reasons for performance problems:

Related Questions

Navigate

• Browse (All)
• Browse S
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.