Autoit and High CPU usage

[Alexxander]

Hi all

everything that i put in the while loop in a non GUI script is making the CPU usage over 25 %

if i used _ispressed or hotkeyset or string funcs or pretty much everything except sleep() is making it 25%

for example try this  "

#include <Misc.au3>
$dll = DllOpen("user32.dll")
While 1
If _IsPressed("0D", $dll) Then enter()
WEnd
func enter()
    msgbox(0, "", "enter")
EndFunc

this small script is making the CPU usage 31% 

this is happening not only on my PC 

how can i make CPU usage much less without using sleep ()    ?

cuz i have some scripts athe really 100 ms or less matters

thanks in advanced

[Melba23]

Alexxander,

Sleep(10) is what I use to keep tight loops from frying the CPU - if that short a pause causes you problems than you probably need to use another language.

M23

[mLipok]

try to use GUIGetMsg()

 

description from helpfile:

"This function automatically idles the CPU when required so that it can be safely used in tight loops without hogging all the CPU."

and in:

GUI Reference - MessageLoop Mode 

"Usually a tight loop like the one shown would send the CPU to 100% - fortunately the GUIGetMsg function automatically idles the CPU when there are no events waiting. Do not put a manual sleep in the loop for fear of stressing the CPU - this will only cause the GUI to become unresponsive."

[BrewManNH]

As I mentioned the last time you said this, without a GUI GUIGetMsg is useless. Use a short sleep as suggested.

[Alexxander]

BrewManNH , mlipok

 

hahahahahah

exactly the same discussion that happened in the last thread

 

<3 u brothers

[mLipok]

sorry @BrewManNH

With all due respect, if you did the test?

Because i did tests

following two scripts

 

 

first script: a non-stop 50% of the CPU

#include <Misc.au3>
$dll = DllOpen("user32.dll")
While 1
    If _IsPressed("0D", $dll) Then enter()
WEnd
Func enter()
    MsgBox(0, "", "enter")
EndFunc   ;==>enter

 

second script: max 1% of the CPU

#include <Misc.au3>
$dll = DllOpen("user32.dll")
While 1
    If _IsPressed("0D", $dll) Then enter()
    GUIGetMsg()
WEnd
Func enter()
    MsgBox(0, "", "enter")
EndFunc   ;==>enter

 

---

AutoIt 3.3.8.1

OS Name Microsoft Windows 7 Professional

Version 6.1.7601 Service Pack 1 Build 7601

Intel ® Core 2 Duo CPU P8700@2.53GHz, 2534 MHz, cores: 2 logical CPUs: 2

---

 

 

please test it on your system, and confirm or deny my findings

Edited September 25, 2013 by mlipok

[BrewManNH]

I'm not saying it doesn't work, what I said was it was pointless to use the function like that. There's no GUI so no need to use GUIGetMsg when a simple Sleep does the same thing. Why over-complicate things by using a function incorrectly, when there's a function that is purpose-built to do it?

[Alexxander]

  On 9/25/2013 at 8:13 PM, mlipok said:

 

sorry @BrewManNH

With all due respect, if you did the test?

Because i did tests

following two scripts

 

 

first script: a non-stop 50% of the CPU

#include <Misc.au3>
$dll = DllOpen("user32.dll")
While 1
    If _IsPressed("0D", $dll) Then enter()
WEnd
Func enter()
    MsgBox(0, "", "enter")
EndFunc   ;==>enter

 

second script: max 1% of the CPU

#include <Misc.au3>
$dll = DllOpen("user32.dll")
While 1
    If _IsPressed("0D", $dll) Then enter()
    GUIGetMsg()
WEnd
Func enter()
    MsgBox(0, "", "enter")
EndFunc   ;==>enter

 

---

AutoIt 3.3.8.1

OS Name Microsoft Windows 7 Professional

Version 6.1.7601 Service Pack 1 Build 7601

Intel ® Core 2 Duo CPU P8700@2.53GHz, 2534 MHz, cores: 2 logical CPUs: 2

---

 

 

please test it on your system, and confirm or deny my findings

 

 

Yes when i put GUIGetMsg() in  my script the CPU usage decreased from  30%  to 4%

but i still find it too much for a super small script

i can't understand why mr.

BrewManNH

 

keep finding it "useless" or "pointless"

anyways thanks a lot 

mlipok

[mLipok]

  On 9/25/2013 at 8:22 PM, BrewManNH said:

There's no GUI so no need to use GUIGetMsg when a simple Sleep does the same thing.

 

if you do not using:

#AutoIt3Wrapper_Change2CUI=y

then

AutoIt always create GUI

see in 

AutoItWinSetTitle Beta HelpFile

#include <GUIConstantsEx.au3>

Example()

Func Example()
    ; Set the title of of the AutoIt Hidden Window.
    AutoItWinSetTitle("My AutoIt Window")

    ; Display AutoIt's Hidden Window.
    AutoItWinShow()

    While 1
        Switch GUIGetMsg()
            Case $GUI_EVENT_CLOSE
                ExitLoop
        EndSwitch
    WEnd
EndFunc   ;==>Example

; Display AutoIt"s Hidden Window. Returns the handle of the window.
Func AutoItWinShow()
    Local $hWnd = WinGetHandle(AutoItWinGetTitle()) ; Get the handle of the AutoIt Hidden Window by finding out the title of the AutoIt Hidden Window.
    WinMove($hWnd, "", (@DesktopWidth / 2) - 250, (@DesktopHeight / 2) - 250, 500, 500) ; Move the AutoIt Hidden Window and re-size for a better view.
    WinSetState($hWnd, "", @SW_SHOW) ; Show the AutoIt Hidden Window, normally this is hidden, but in the interest of this example I"m displaying it.
    Return $hWnd
EndFunc   ;==>AutoItWinShow

So there is a GUI, but mostly about him does not remember.

At least, I think that about this.

If anyone has other thoughts, then I be happy to take them.

[JLogan3o13]

And a sleep(10) will reduce it the same. I don't know how lousy a CPU you have, but it took 29% on mine without the sleep. Adding the sleep took it down to 3%.

@mlipok - just because by some chance GUIGetMsg works in this case doesn't mean using a GUI function in a non-GUI script is good coding practice. If you're going to "help" forum users, you should be suggesting the right tool for the job. Why complicate matters when a simple sleep will work?

Edited September 25, 2013 by JLogan3o13

[Jos]

@mlipok,

Using GUIGetMsg() is not the correct advice and is confusing. You should use sleep(xx) in stead as suggested by BrewManNH and JLogan3o13.

The fact that AutoIt3 creates a hidden GUI doesn't bare any relation to using GUIGetMsg().

 

  On 9/25/2013 at 8:23 PM, Alexxander said:

 

Yes when i put GUIGetMsg() in  my script the CPU usage decreased from  30%  to 4%

but i still find it too much for a super small script

i can't understand why mr.

BrewManNH

 

keep finding it "useless" or "pointless"

anyways thanks a lot 

mlipok

 

 

You clearly haven't understood anything suggested by BrewManNH and JLogan3o13 so maybe you should read it again before making these dumb statements.

Jos

Edited September 25, 2013 by Jos

[JLogan3o13]

I have to admit credit goes to BrewManNH for (properly) suggesting Sleep in both this and the previous topic. I just had to add my 2 cents as to how dumb it is suggesting the wrong tool

[Melba23]

mlipok,

I entirely agree with JLogan3o13 - there is no point in using GUIGetMsg unless you are looking to get a return from the message system about an actioned control as it is purely by chance that there is a built-in delay within the function to prevent the CPU getting overheated. If there is no GUI being used by a MessageLoop mode script itself then there is no point in suggesting that people use the GUIGetMsg function rather than the function designed to pause the script. The fact that there is always a hidden Autoit GUI has nothing to do with anything - that is a just requirement of AutoIt to access the system.

Using GUIGetMsg to reduce CPU load in any other form of script is only going to confuse. Think about an OnEvent script - would you suggest using GUIGetMsg inside its idle loop? Of course not - you would suggest Sleep. So please do not continue with this approach which risks the opposite of what we should aim to do - clarify AutoIt coding for those who seek help here.

M23

[mLipok]

All right.

 

I took all the attention, to my knowledge.

 

I'll try to think about it thoroughly.

Of course, I no longer suggest such solutions.

 

Though it is possible that at some unspecified time in the distant future, I will ask a more precise question, of course, in a separate thread.

I hope that edit: if not in this case, not offended at me, just as I hope not offended now.

 

Greetings to all and I apologize for putting confusion.

Edited September 25, 2013 by mlipok

[Melba23]

mlipok,

 

  Quote

Though it is possible that at some unspecified time in the distant future, I will ask a more precise question, of course, in a separate thread

Please do.

 

  Quote

I hope that in this case, not offended at me, just as I hope not offended now

No-one should feel offended - all we are trying to do is make sure that the best advice is given to those seeking help here.

M23

[diehardfans]

guigetmsg() is the key, thks

[water]

This thread is nearly 5 years old. Don’t necro old threads just to say ‘thks’  

[TheDcoder]

@diehardfans Also GUIGetMsg is only useful if you have an active GUI created by the script, else use Sleep(10) like it has be said many times previously in this thread

[JLogan3o13]

  On 8/24/2018 at 12:56 AM, diehardfans said:

guigetmsg() is the key, thks

Expand  

Not only did you resurrect a very old post, but you completely missed the point of it. Please read through it again, and please refrain from bringing old posts back to life, especially when you are adding nothing to the conversation.