There are many reasons that could lead to the users experiencing slowness, by understanding the root cause of the system slowness, we will be able to troubleshoot effectively. In order to resolve the problems effectively, it is extremely important for the users to provide the details. To some users, slow means if a page is loaded more than 2 seconds, while slowness could mean 20 seconds for the same page to be loaded. Instead of using qualitative words (big , small, slow, fast, good, not good), we will use quantitative words while communicating with the engineers who is going to help you in seconds, minutes, hours, date / time etc. Also, in order to be specific, we are going to indicate which page is slow, and which page (function / screen / module) takes how many seconds to load, and how many seconds to generate a certain report. And if we are generating the report, we will indicate exactly which date range, which branches / company, what category filter or settings we use to generate the reports. All this information is essential for us to help you identify the root cause quickly, and resolve the problems effectively.
Possible Root Cause of the System Slowness, Detection, and Solutions
| No | Possible Root Cause | Troubleshooting Guide | Solutions |
|---|---|---|---|
| 1 | Client Device
| The fastest way to check if the slowness is caused by the client device, is to access the same website / functions with multiple other devices. If Accessibility from other devices are normal, then the probability of slowness caused by the slowness in the device itself is almost certain. Regardless of whether it is mobile or desktop devices, see below for more steps to identify the root cause:
Apart from System Performance monitoring, it is never alien to our technical support team that some of the client devices that have been infected by Virus is known to perform badly. Usually, when we detected high CPU usage, and high Network Bandwidth, we would also be recommending the users to install anti-virus software to detect the potential security threat to the devices. Another possibility is the web browser. When it comes to web-browser usage, settings, the following areas could be checked:
| Depends on the root cause from the troubleshooting of the client device, users could upgrade the RAM, Processor, or perform anti-virus scanning accordingly. At the time of reading, the following guide may be out-dated, but google is your best friends, there are plenty of resources available online to resolve the problems that you are having with optimizing your devices.
|
| 2 | Client Local Area Network | When devices are not connected directly to the internet, it is possible it goes thru routers, switches, proxy servers and other possible network routes to access the Wavelet EMP on the cloud. There are a few ways to check and detect if the problems are caused by the Local Area Network:
| |
| 3 | Client Internet Connectivity | ||
| 4 | Public Internet | ||
| 5 | Data Center Network | ||
| 6 | Server Network | ||
| 7 | Server Operating Systems | ||
| 8 | Server Application Server | ||
| 9 | Server Database Server | ||
| 10 | Server Hard Disk | ||
| 11 | Wavelet EMP Itself | ||
| 12 | Usage of EMP |