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

normal Configure loop 100 to run 2 loops

  • merrist
  • merrist's Avatar Topic Author
20 Feb 2013 08:20 #803 by merrist
merrist created the topic: Configure loop 100 to run 2 loops
Hi,

If I want that the loop of the session 100 is configurated as 2 loops. What should I need to do?

Kind Regards,

Jack

Please Log in to join the conversation.

More
21 Feb 2013 10:24 #808 by d.geerlings
d.geerlings replied the topic: Configure loop 100 to run 2 loops
Jack,

Is session 100 the last session in your test? In that case you can set the autologoff timeout to 1000. This will make sure that the test is still active after the last session has finished it's first loop (roughly 15 minutes or 900 seconds). Since the test is still active the last session will start another loop.

Please Log in to join the conversation.

  • merrist
  • merrist's Avatar Topic Author
30 May 2013 03:12 #1056 by merrist
merrist replied the topic: Configure loop 100 to run 2 loops
Moderator,

I don't understand the autologoff timeout value.

The autologoff timeout value is the test time for each session, is such?

Kind Regards,
Jack

Please Log in to join the conversation.

More
17 Jun 2013 12:37 #1156 by o.bouhaj
o.bouhaj replied the topic: Configure loop 100 to run 2 loops
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

Shai Maskit - Kaminario

“We tested 750 seats so customers can compare Kaminario with solutions from other vendors. It really comes down to delivering the best user experience at the right price point. As soon as we show the solution and that it has been validated by Login VSI customers can rest assured that it will fit the rest of their environment.”

Shai Maskit, Director of Product & Solutions at Kaminario


Johnny Blizzard - Health Insurance Organization

"We now have indisputable empirical proof supporting our claims. With Login VSI, we can run our own applications against various hardware platforms before we move to production! Application owners can see how their code impacts their users on our systems and we can present our findings to management for funding increases. We can also advocate for the users when supporting their claims of poor performance, all because of Login VSI."

Johnny Blizzard, Sr. IT Systems Engineer at a Health Insurance Organization


Michael Bernas - Workers' Compensation Board Alberta

“We've used Login VSI for the past 3 years as part of our Disaster Recovery Exercise. It's not only helped us in validating the functionality of our Citrix XenApp farm, but it's also been an invaluable tool in proving the number of concurrent connections into the environments. It’s allowed us to take our theoretical numbers and put actual real life data behind them.”

Michael Bernas, Workers' Compensation Board of Alberta

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