View Single Post
Lt. Commander
Join Date: Dec 2007
Posts: 120
# 13
11-23-2011, 03:56 PM
Originally Posted by Sardoc
As a programmer, if I was testing this, I wouldn't need actual users to test it out... I'd just create a bunch of simulated logins (actual logins as far as the server is concerned) during that time, and analyze the results on that. As users would get affected during that time, just inform people that the test is going on, do the test, some might get stuck during that time, but all I care about in monitoring the full queue.

20 minutes is plenty of time to perform a test, if done right
The server might handle the queue just fine, but the client also needs to work in the queue scenario.
One issue they had in DCU was that in some cases the client wouldn't go into queue mode and make the client freeze on loading screen or that the server took too long to give an update regarding the queue so that the client terminated the connection due to time out and thought it had been disconnected.

Hammering the server with simulated logins is one way of testing it, but nothing beats the same amount of logins from real players that gets frustrated at ending up at # 1000 or think that they are stuck so they log out and back in again several times to get to a lower # that will generate allot more stress on the login queue than simulated ones.