login vsi company logo login vsi company logo 250x40
header-05.jpg

normal auto logoff timeout

  • neokylin
  • neokylin's Avatar Topic Author
26 Jul 2013 09:18 #1330 by neokylin
neokylin created the topic: auto logoff timeout
hi,
i have enable the "auto logoff" option,But I am confused whether the "timeout " come into use when the last session ended for the setup time and close all the dialogues or it will come into use when each of the session ended for the setup time and close them one by one?

Please Log in to join the conversation.

More
26 Jul 2013 14:56 #1332 by o.bouhaj
o.bouhaj replied the topic: auto logoff timeout
Hi Neo,

If you enable the 'auto logoff' option:
VSI will then launch all the test users/sessions and when the _last_ user/session is launched - the time that you setup for 'auto logoff' will start.

We do this to make sure that each session runs the test.


The idea behind logoff concept?

Let’s say, You are telling VSI to wait an additional 1800 seconds (30 minutes) before indicating sessions can log off. Set the autologoff timeout back to 120 and sessions will start logging off 2 minutes after the last session has been launched.

This is how it works. Assuming 20 session, 30 second interval and 120 second logoff timeout.
00:00 session 1 is launched. It takes a few seconds to log on and become active.
00:12 session 1 is done logging on, has started the main VSI executable and is now considered active.
00:30 session 2 is launched. It takes a few seconds to log on and become active.
00:44 session 2 is done logging on, has started the main VSI executable and is now considered active.
(these steps repeat up to session 20)
10:00 session 20 is launched. The system is under a reasonable amount of load so log on takes a while. Lets say 50 seconds.
10:01 VSI notices all of the 20 sessions have been launched. It would have indicated to the active sessions that they can start logging off, EXCEPT that there is a autologoff timeout. VSI will wait an additional 120 seconds, the configured autologoff timeout, until indicating session can log off.
10:50 session 20 is done logging on, has started the main VSI executable and is now considered active.
12:01 the autologoff timeout has expired. VSI indicates sessions can start logging off AFTER their current loop is done.
15:12 session 1 is done with its first loop. Session 1 notices VSI has indicated that sessions can start logging off. Session 1 logs off.
15:43 session 2 is done with its first loop. Session 2 notices VSI has indicated that sessions can start logging off. Session 2 logs off.
(etc. etc. up until all sessions eventually log off)

Let’s look at 20 sessions, 30 second interval, 1800 second autologoff timeout.
00:00 session 1 is launched. It takes a few seconds to log on and become active.
00:12 session 1 is done logging on, has started the main VSI executable and is now considered active.
00:30 session 2 is launched. It takes a few seconds to log on and become active.
00:44 session 2 is done logging on, has started the main VSI executable and is now considered active.
(these steps repeat up to session 20)
10:00 session 20 is launched. The system is under a reasonable amount of load so log on takes a while. Let’s say 50 seconds.
10:01 VSI notices all of the 20 sessions have been launched. It would have indicated to the active sessions that they can start logging off, EXCEPT that there is a autologoff timeout. VSI will wait an additional 1800 seconds, the configured autologoff timeout, until indicating session can log off.
10:50 session 20 is done logging on, has started the main VSI executable and is now considered active.
(sessions are running and not much happens other than that)
15:12 session 1 is done with its first loop. A loop takes about 15 minutes. Since VSI has not indicated the sessions can start logging off yet session 1 will start another loop.
15:44 session 2 is done with its first loop. Since VSI has not indicated the sessions can start logging off yet session 2 will start another loop.
(this eventually happens for all 20 sessions)
30:12 session 1 is done with its second loop. Since VSI still has not indicated the sessions can start logging off session 1 will start another loop.
30:43 session 2 is done with its second loop. Since VSI still has not indicated the sessions can start logging off session 2 will start another loop.
(this happens for every session that completes a loop up to 40:00)
40:01 the autologoff timeout has expired. VSI indicates sessions can start logging off AFTER their current loop is done.
(some sessions start logging off as their loop finishes)
45:12 session 1 is done with its third loop. Session 1 notices VSI has indicated that sessions can start logging off. Session 1 logs off.
45:43 session 2 is done with its third loop. Session 2 notices VSI has indicated that sessions can start logging off. Session 2 logs off.
(etc etc up until all sessions eventually log off)

Notice how, without the autologoff timeout, session 20 would never become active. That is the idea behind the timeout, allow the last few sessions enough time to log on and become active. Setting the timeout higher and higher just extends the duration of the test.

Please Log in to join the conversation.

What our customers are saying

Sajad Shah - Cancer Research

"Login VSI has empowered us to make more informed decisions on releasing a new vDisk which we now do on a monthly basis. We have found that Login VSI tests can also flag other issues in our environment that may not be picked up by our standard User Testing which allows us to either make the appropriate changes to the vDisk or workload script adjustments to run successful tests. This has given us peace of mind and allows us to release VDI’s with confidence."

Sajad Shah, Senior Technical Analyst at Cancer Research UK


Michael Mainusch - Dachser

“With Login VSI, we can simulate the effects and compatibilities of applications and patches, as well as scaling in a virtualized terminal server environment, with minimal expenditure of time. Due to the adaptability of Login VSI to individual customer environments, we can simulate the real production environment, using the achieved measurement results and assertions.”

Michael Mainusch, Team Leader Application Services at Dachser


Tony Reynolds - 23Technology

"As a cloud and virtualisation consultancy, 23Technology use Login VSI to prove the scalability of our paper designs for our customers. It has become an important part of our assurance process. In one instance, it helped us to successfully complete a project by showing that, with correctly configured anti-virus, the designed solution scaled to meet our client’s needs."

Tony Reynolds, Technical Director at 23Technology

Login VSI, Inc.

300 Tradecenter

Suite 3460
Woburn, MA 01801

Phone: +1 844 828 3693

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200