I am working with Dashesh on this issue.
We will enable the TestRail logging and accumulate data from 6 different users (3 regular users and 3 light users. 6 different desktops). Then, we will provide the response time it gathered.
Since the number of users is relatively small and the web server will be only available within our intranet, we are not concern about the network traffic to this server. Currently, we only have TestRail running in IIS and the only other application we planned to deploy with is Redmine.
By the way, we are using virtual machine to evaluate TestRail. We didn’t request a DNS A record through our IT department. All users are accessing the server via IP address (http://xxx.xxx.xxx.xxx/ since using the default web site port 80). Also, we are seeing this occurred within the server via http://localhost/ or directly http://localhost/index.php?/auth/login.
I am looking into IIS configuration since I suspect it is the source of this behavior. So far, I didn’t find any potential setting may resolve this.
By the way, we have similar issue with our temporary Redmine server (RoR + Mysql + Thin + IIS) use for TestRail evaluation/integration test. It is located on a different vm. Due to minimal amount of traffic on that server, the idle timer for the corresponding application pool worker process is disabled in IIS. It resolved the issue of ‘slow/warmup’ required after long inactivity in Redmine. Same setting didn’t resolve the similar issue with TestRail.
It is not a significant issue but just an annoying one.