in stress test ,some autoit process not exit normally

[px307]

recently i am doing stress test, our application is using java to run autoit script on windows2008 ,
the java code is :

   Runtime.getRuntime().exec("cmd /c AutoIt3.exe test.au3")

the script content of test.au2 is only one line :

Exit 0

when the command  run one by one ,all is normal ,but when the command run simultaneously, concurrent count is about 30, 
after a few minute stress test, we found that some  AutoIt3.exe process  never normal exit, they alway exist in process list.
if i run system command ,for example:   exit 0 

not autoit3.exe ,  all processes normal exit, i guess there is some wrong in Autoit3.exe

how to trace the problem or avoid , thanks

the version of Autoit3.exe is 3.3.14.2

[Earthshine]

What is the purpose of the stress test going to prove? Why would you run exit 0? Not understanding 

Edited January 20, 2018 by Earthshine

[careca]

So you run 30 scripts at the same time, and wonder why there are issues, im not surprised honestly.

" not autoit3.exe ,  all processes normal exit "

huh?

[px307]

12 hours ago, Earthshine said:

What is the purpose of the stress test going to prove? Why would you run exit 0? Not understanding 

because our application uses autoit to run script  heavily ,we want to prove that it can  run 30 scripts at the same time stably for 2 hours, for avoid possible  side effect of script self, we choose the simplest script:  exit 0 

 

5 hours ago, careca said:

So you run 30 scripts at the same time, and wonder why there are issues, im not surprised honestly.

" not autoit3.exe ,  all processes normal exit "

huh?

we run  " cmd /c exit 0  " instead of "cmd /c autoit3 .... "  simultaneously ,  then all processes can normal exit, but with autoit3,  most processes can  normal exit , yet  a few autoit3 process never exit,  we must kill them from task manager

 

please help me  trouble shoot the problem , does  anybody do similar test ? 

thanks

 

[careca]

Just compile the scripts and run them, test that way. I really dont believe autoit was designed to run 30 scripts simultaneously. Why would you ever need that?

You test one (maybe 2 or 3 at the same time) script, compile it, done.

@Jos: What do you think about this? Is this abnormal behaviour?

[Jos]

8 hours ago, careca said:

I really dont believe autoit was designed to run 30 scripts simultaneously.

I honestly do not understand this statement, nor why "some autoit scripts" would not finish as they are all run autonomously. 

@px307,
What does hanging mean? do you see their icon's still in the system tray? 
How exactly do you manage to shell 30 times a script that only have the line "exit 0" in it without the first one being ended?

Jos

[jchd]

Do you experience the same issue if you compile your script once, then launch 30 or more instances of this .exe?

 

[careca]

@Jos I think i see where my assumption failed, i cannot run two, running them in SciTe that is.

If i call the exe on a number of scripts by batch file or something it's supposed to work.

[Bowmore]

I have successfully run multiple copies of the same AutoIt script shelled from a parent application with different parameters. The most I have run is 32 on a server with 32 cores,  although generally it is in the range 8 to 12 on my local workstation. So what you are trying to do is perfectly possible. Some things to try

1 Try adding a sleep()  for a random length of time or a loop doing something  a few times before the Exit 0, to give the script some actual work to do. It may be that your test script is too simple

2 Try starting with launching a smaller number of scripts e.g. 5 to see if it that works and gradually work up 30.

3 Keep a watch on the CPU utilisation. I may be that 30 is just too many for your hardware.  

4 Try slowing the speed at which your Java application can launch a new script by adding a short delay after this line

Runtime.getRuntime().exec("cmd /c AutoIt3.exe test.au3")

 

[Jos]

This example runs 100 concurrent AutoIt3 processes without any issues on my laptop and all AutoIt3 processes cleanly close after 10 seconds:

#include<File.au3>
$Filename = _TempFile(@ScriptDir,"~" ,".au3")
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $Filename = ' & $Filename & @CRLF & '>Error code: ' & @error & @CRLF) ;### Debug Console
FileWriteLine($filename,"Sleep(10000)")
FileWriteLine($filename,"Exit")
For $x = 1 to 100
    run('"C:\Program Files (x86)\AutoIt3\AutoIt3.exe" "' & $filename & '"',@ScriptDir)
Next
sleep(1000)
FileDelete($filename)

Jos

[jchd]

I still wonder what is the rationale to run any number of source scripts thru AutoIt3.exe instead or running the as many instances of the compiled .EXE. Is there any?

[Jos]

I don't think there is any pro or con to it to be honest as to me they are the same. 

Jos

[jchd]

There are significant differences: the stand-alone interpretor has a large footprint by itself, hence N times its actual footprint, has to fetch N times all the includes the source requires (I agree there seem to be none in the OP example but there will be some in any practical-use source), etc.

[Jos]

The "compiled script" is the interpreter binary packed with the tokenized script, so agree it could take a little longer in case there are many included files to pickup, but that is only at startup, but other than that, the processes are more or less comparable.

I just tested this way to compare the memory footprint for AutoIt3 and the compiled script and they were more or less the same as expected:

For $x = 1 to 10
    run('"C:\Program Files (x86)\AutoIt3\AutoIt3.exe" "atestshell.au3"',@ScriptDir)
Next
For $x = 1 to 10
    run("atestshell.exe",@ScriptDir)
Next

 

Jos

[jchd]

Sure but as you know the devil is often in the details.

OTOH somethingelse is maybe the source of OP's issue, AV or something else exterior to AutoIt stuff.

[Earthshine]

 Maybe executing so many at once causes a deadlock somewhere, yes 

[czardas]

I have run a random number of scripts (each for a random period) - controlled by a master script in an infinite loop - and never encountered any problems.

Edited January 21, 2018 by czardas

[Gianni]

I also run run many scripts (even not compiled) and I collect responses from those scripts from a main script without issues.
For example, this udf (https://www.autoitscript.com/forum/topic/156395-versatile-multi-ping/#comment-1131267) runs more ping commands at the same time and collects results from each of them.
Here (https://www.autoitscript.com/forum/topic/177999-how-to-change-bgcolor-of-a-control-belonging-to-another-window/?do=findComment&comment=1278754) a funny example where a main script with a gui with 100 labels, spawns 100 separate and not compiled scripts that will change the content and the color of the main gui (save the last 2 script Main.au3 and Child.au3 in the same path and run the Main.au3). When the main script ends, also all child processes will close themselves. it was just for a fun experiment