WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

Launching WinBatch and Other Apps
plus

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Running Several Instances of a Script and Slowdowns

Keywords: 	 CPU usage multiple Winbatches

Question:

We're using WinBatch to simulate multiple users on an Oracle database application running in Winframe 1.8. Our regular test tool wouldn't work with the ICA Win protocol so we recorded a script using WinBatch. We are able to get the script to open the application, login and send keystrokes to several windows and eventually close the application. This tool was recommended by the Citrix people to perform this testing.

The problem we're having is that when we get to around 20 sessions simulating 20 concurrent users, we notice the script slowing down. It appears that the WinBatch script is processing the users in some sort of sequence. This is bad for our application of your program since we need to simulate an actual stress to the application, as it will be when released for use. The WinBatch script were running has been compiled into an executable file which is launched in the Winframe 1.8 environment. What can we do to have WinBatch run the script as fast for many users as it is run for one user ? Are we implementing this incorrectly ?

It's not my machine getting bogged down since the scripts are running on a separate server (Winframe 1.8 Server). The scripts seem like they are waiting for one to finish a task before they continue a task for a different user. It's more like they are all running from the same script instead of a separate instance of the script.

Answer:

It would seem to depend a lot on the script.

And if all the scripts are running one one poor machine, that means that the poor machine trying to emulate 20 users and run 20 winbatch scripts. I would expect some slowdowns. I would think it rare that one machine has 20 people trying to use it at the same time.

It *may* also kind of depend how they launch the 20 scripts. And how they keep those twenty scripts from stomping on top of each other.

WinBatch itself, when running, occupies maybe 600K of memory. The number of simultaneous Winbatch scripts that can run on any given machine depends upon the available memory on that PC. Certainly, the more Winbatch scripts you have running, the more system resources are used. You can see, for example, if you have a number of scripts running that they all run a little more slowly the more you run.


Article ID:   W14250
Filename:   Running Several Instances of a Script.txt
File Created: 1999:10:26:11:22:48
Last Updated: 1999:10:26:11:22:48