The terminal discovery task for a site takes about 5 minutes. On the Terminal Access Record page, it is found that more than 30 thousand terminal users exist.
Generally, the slow response issue is caused by the high memory/CPU usage of the server. Check whether the memory/CPU usage of the server is too high.
Windows: Open Windows Task Manager. As shown in the following figure, the java.exe and sqlservr.exe processes (which are related to eSight) occupy a large amount of memory. Check eSight services.
Linux: Run the top command to check the processes that occupy a large amount of memory. As shown in the following figure, the java and oracle processes are related to eSight.
The following features of eSight probably cause the slow response issue of eSight: automatic device discovery, automatic terminal discovery, performance data collection, interface polling by group, NE alarm synchronization, scheduled backup tasks, AP information polling, access user information polling, and report tasks.
1. In eSight\appbase\var\iemp\log\iemp\roa\roatask.log (including the time suffix, for example, roatask_20180415201916132.log), search for the keyword "cost" to find the log about the request with the longest execution time.