Understanding and defining the performance problem
There are many components involved that can affect performance. As an initial step, it is recommended to identify the component within the hardware and software stack, which is causing the performance problem before going into details in the second phase.
The following questions should help you to narrow down a performance problem to a specific
component or will help others to start investigations in case assistance is required, for example
from support or services.
- What exactly is slow:
- only a specific use case (for example, opening an item from a specific catalog in the user interface, what container scripts, specs, views are used, do you see specific errors in the appsvr service log files, and so on.)
- general slowness, which affects all user interface interactions and scheduled jobs (this can point to some basic configuration or maintenance deficiencies or resource bottlenecks).
- When did the problem manifest:
- did performance degrade over time (old version data or general database maintenance, for example reorganize, update statistics might help), or
- was there an abrupt change in performance after, for example, some new application customization (what has been changed, spec definition, container script, and so on.) Or, was there some large data processing, for example with import or report, task (update statistics, need to reorganize database tables).
- Who is affected:
- All users working with the user interface, or
- only specific users (do they do specific tasks, do they have specific permissions, are they located in a different location or network, what workstation and Internet Explorer version are they using)