Script becomes way slower after a msgbox - (Moved)

[Jos]

I understand but you have to see this a little in perspective as the loop currently really doesn't do anything and, like you said, when for some reason extra things need to be checked by this single threaded process, the efficiency is bound to become less.

Simple example that makes the factor 2 for me:

$x = 0
$start = TimerInit()
For $i = 1 To 500000
    $x = WinGetHandle("[ACTIVE]")
Next
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : TimerDiff($start) = ' & TimerDiff($start) & @CRLF) ;### Debug Console
; Show AutoIt3's hidden window
WinSetState(AutoItWinGetTitle(), "", @SW_SHOW)
$start = TimerInit()
$x = 0
For $i = 1 To 500000
    $x = WinGetHandle("[ACTIVE]")
Next
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : TimerDiff($start) = ' & TimerDiff($start) & @CRLF) ;### Debug Console

Agreed it is still substantial, but this was merely to counter the 600% to 1000% and put that in perspective. 
I would not know myself how I could debug this so there is no other option than to wait for @Jon unless @jpm knows how to tackle this.

Jos 

Edited April 5, 2020 by Jos

[Nine]

I am nowhere comparing AutoIt speed with C++ or any other languages.  I am comparing AutoIt with itself.  It should be as fast on any Windows version.  I have no problem with GuiOnEventMode as it is comparable between 7 and 10.  But the GUI speed issue is definitely not trivial.  I would love to give you a hand on solving this, but I am not sure I would be able to help.

[jchd]

The only way out is debug-compile the source and step-debug compare a W7 example against the same under W10 in two bare-bones virtual machines.  valgrind could also greatly help.

Here we're hopelessly impotent.

Of course this issue won't prematurely trigger turning the sun into a red giant, but still.

[argumentum]

On 4/2/2020 at 11:12 AM, Nine said:

Confirmed.  on Win10 the scale is similar as yours 10x slower after the MsgBox.

$x=0
$start=TimerInit()
for $i=1 to 500000
    $x+=1
Next
$start = Round(TimerDiff($start), 5)
ConsoleWrite('Round 1 = ' & $start & @CRLF)
MsgBox(0,"",$start) ; Round 1 = 58.10089

$start=TimerInit()
$x=0
for $i=1 to 500000
    $x+=1
Next
$start = Round(TimerDiff($start), 5)
ConsoleWrite('Round 2 = ' & $start & @CRLF)
MsgBox(0,"",$start) ; Round 2 = 56.70231

maybe a hardware thing ?, no clue. I can not replicate the issue.

Edit 1: same goes with the WinGetHandle

$x = 0
$start = TimerInit()
For $i = 1 To 500000
    $x = WinGetHandle("[ACTIVE]")
Next
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : TimerDiff($start) = ' & TimerDiff($start) & @CRLF) ;### Debug Console
; Show AutoIt3's hidden window
WinSetState(AutoItWinGetTitle(), "", @SW_SHOW)
$start = TimerInit()
$x = 0
For $i = 1 To 500000
    $x = WinGetHandle("[ACTIVE]")
Next
ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : TimerDiff($start) = ' & TimerDiff($start) & @CRLF) ;### Debug Console

;@@ Debug(25) : TimerDiff($start) = 909.692171252823
;@@ Debug(33) : TimerDiff($start) = 825.419178988507

Edit 2: 

For $n = 0 To 1
    AutoItSetOption('GUIOnEventMode', $n)
    $x = 0
    $start = TimerInit()
    For $i = 1 To 500000
        $x += 1
    Next
    ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : TimerDiff($start) = ' & TimerDiff($start) & @TAB & ' GUIOnEventMode = ' & $n & @CRLF) ;### Debug Console
    ; Show the AutoIt3 hidden window
    WinSetState(AutoItWinGetTitle(), "", @SW_SHOW)
    $start = TimerInit()
    $x = 0
    For $i = 1 To 500000
        $x += 1
    Next
    ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : TimerDiff($start) = ' & TimerDiff($start) & @TAB & ' GUIOnEventMode = ' & $n & @CRLF) ;### Debug Console
Next
;@@ Debug(44) : TimerDiff($start) = 58.4976299233912     GUIOnEventMode = 0
;@@ Debug(52) : TimerDiff($start) = 56.4975617675848     GUIOnEventMode = 0
;@@ Debug(44) : TimerDiff($start) = 143.726465813906     GUIOnEventMode = 1
;@@ Debug(52) : TimerDiff($start) = 143.86776443691  GUIOnEventMode = 1

As far as OnEvent, it does have an impact.

Edit 3: 

$nStart = TimerInit()
$iX = 0
For $i = 1 To 500000
    $iX += 1
Next
ConsoleWrite("Initial: " & TimerDiff($nStart) & @CRLF)
$hGUI = GUICreate("Test", 10, 10)
$nStart = TimerInit()
$iX = 0
For $i = 1 To 500000
    $iX += 1
Next
ConsoleWrite("Created: " & TimerDiff($nStart) & @CRLF)
GUISetState(@SW_HIDE)
$nStart = TimerInit()
$iX = 0
For $i = 1 To 500000
    $iX += 1
Next
ConsoleWrite("Hidden: " & TimerDiff($nStart) & @CRLF)
GUISetState(@SW_SHOW)
$nStart = TimerInit()
$iX = 0
For $i = 1 To 500000
    $iX += 1
Next
ConsoleWrite("Shown: " & TimerDiff($nStart) & @CRLF)
;Initial: 57.5254399859034
;Created: 56.5734751454337
;Hidden: 58.4333529027309
;Shown: 58.930668644478

It all look good in my PC. I guess that to debug this we are gonna have to share every detail of the PC environment ( software and hardware ). 

Edit 5: ..tried on other PCs. The one that shows these bugs have Hyper-V running.
Edit 6: is not the Hyper-V, as I just remoted in to a PC just like the one I have at home but running Hyper-V and it showed none of the problems.

Sorry about all these edits but I'm trying to find the reason that produces the events/mishaps. 

 

Edited April 5, 2020 by argumentum

[jchd]

Thanks for the reality check pointing to hardware and/or drivers and/or OSversion, that's a big step toward pinpointing the culprit.

I'm afraid then that it won't be so easy to do due to the vast diversity of platforms.

[Melba23]

argumentum,

Are you running Win10 x32 or x64? 

M23

[water]

My results:

Test1:
Round 1 = 112.6326
Round 2 = 113.9268

Test2:
@@ Debug(25) : TimerDiff($start) = 1447.3477
@@ Debug(33) : TimerDiff($start) = 1355.7156

Test 3:
@@ Debug(50) : TimerDiff($start) = 110.05     GUIOnEventMode = 0
@@ Debug(58) : TimerDiff($start) = 110.5822     GUIOnEventMode = 0
@@ Debug(50) : TimerDiff($start) = 226.943     GUIOnEventMode = 1
@@ Debug(58) : TimerDiff($start) = 226.5295     GUIOnEventMode = 1

Test 4:
Initial: 123.4077
Created: 110.2741
Hidden: 118.9294
Shown: 123.3573

Can we create a script that grabs all information needed to find the cause of this performance problem (WMI created from Scriptomatic comes to my mind)?

Edited April 5, 2020 by water

[MrCreatoR]

Check this out:

 

$x=0
$start=TimerInit()
for $i=1 to 500000
    $x+=1
Next

ConsoleWrite(TimerDiff($start) & @CRLF)
_ThreadStart("_Thread")

$start=TimerInit()
$x=0
for $i=1 to 500000
    $x+=1
Next

ConsoleWrite(TimerDiff($start) & @CRLF)

Func _Thread($vDummy)
    MsgBox(0, "", '', 1)
EndFunc   ;==>_Thread1

Func _ThreadStart($sFunctionName)
    Local $h1, $h2, $h3 = DllStructCreate("hwnd[1]"), $h4 = DllStructGetPtr($h3)
    
    $h1 = DllCallbackRegister($sFunctionName, "int", "int")
    $st = DllStructCreate("int")
    $h3 = DllCall("Kernel32.dll", "hwnd", "CreateThread", "ptr", 0, _
            "int", 0, _
            "ptr", DllCallbackGetPtr($h1), _
            "int", 0, _
            "int", 0, _
            "ptr", DllStructGetPtr($h2))
    
    DllStructSetData($h3, 1, $h3[0], 1)
    DllCall("Kernel32.dll", "int", "CloseHandle", "hwnd", DllStructGetData($h3, 1, 1))
EndFunc   ;==>_ThreadStart

After the thread starts the second results (for me) even faster than the first one...

[argumentum]

2 hours ago, Melba23 said:

Are you running Win10 x32 or x64? 

Win10 x64 but I run AutoIt in x86 ( I don't run or compile x64 unless needed ) 

Edit: Just run all the examples as x64 and x86. No problems.

Edit 2: ..also changed my High Contrast theme to regular theme, back and forth. All good. 

Edited April 5, 2020 by argumentum

[argumentum]

56 minutes ago, MrCreatoR said:

After the thread starts the second results (for me) even faster than the first one

That is quite common.

[Nine]

It is kind of odd that everyone sees the problem except you @argumentum.  You must have unique setup.  It would be great if you could change your setup to get the same result of us, and pinpoint the setup solution that makes you invincible...

[argumentum]

...working on it..

[Nine]

@MrCreatoR we already know that since long.  Maybe read the whole thread ?

[water]

I too do not see the problem based on argumentum‘s scripts. I posted my results above. 

[argumentum]

win 10 2016 ( version 1607 ) don't show the problem. @water, what Win10 are you running without issues ?

Edited April 5, 2020 by argumentum

[argumentum]

That is it, 1909 has the issue, 1607 does not. I would have to make virtual PCs, with every mayor version to find exactly when it started. But I rather not unless needed.

[Nine]

1 minute ago, argumentum said:

That is it, 1909 has the issue, 1607 does not. I would have to make virtual PCs, with every mayor version to find exactly when it started. But I rather not unless needed.

That is a great finding, hope it will help to solve the issue.  Thanks a lot.  I don,t think it is necessary to find WHEN exactly it has started.  Now the problem is to find out WHY ?

[water]

I run Windows 10 Enterprise, Version 10.0.17134 Build 17134 (HAL 1098)

Edited April 5, 2020 by water

[MrCreatoR]

16 minutes ago, Nine said:

we already know that since long.  Maybe read the whole thread ?

I did, and i didn't sow anything like those results.

I am just trying to find a solution since i know about this issue long time ago.

[argumentum]

2 minutes ago, water said:

Version 10.0.17134

that's version 1803