AutoHotkey Community

Result from AutoIt
CPU Usage : 50%
Mem Usage : 4,260K
Elapsed Time : 24.9107499785605 (Secs)






Result from AutoHotkey
CPU Usage : 50%
Mem Usage : 3,856K
Elapsed Time : 6.450900 (Secs)



"AutoIt is 4x slower" is my answer

While() not only loops, but also checks for the expression to be true. I think for a fair comparison, that AHK should have to use an if statement in the loop, to check if i is not equal to 1,000,000. Also, AutoIt does not have a SetBatchLines command that I am aware of.

_________________
Religion is false. >_>

exact time measurement for a 100 femtoseconds accuracy.
I like atomic clocks!!

Trikster, so you are saying that he should give AutoIT a chance by slowing down AHK ?

Not really, I just think we should give them a level playing field

Edit: I just saw the humor in your post

_________________
Religion is false. >_>

If you don't use SetBatchLines, -1 AHK uses only 25% cpu while AutoIt uses 50% cpu by default. which isn't fair.



Elapsed Time : 11.761779 (Secs)

AutoIt is still more than 2x slower even AHK brakes itself. there will be no arguments on performance comparison. AHK is much more superior to AutoIt in this area

...I think for CPU measurements you should note if you have either a "dual core CPU" or 2 or more CPU's...AHK using 25% CPU seems to suggest to me it's using 50% of the CPU it was given...or 50% of the "core" it was given...for example on my computer, I have 1 CPU & 1 core...so on loops like that (I have not tested yours yet) AHK would probably use 50% CPU & AutoIT would probably use 100% CPU...based on 1 CPU 1 core...

I think I would want a computer with more CPU's &/or more cores, but seeing 25% CPU usage in Task Manager when right now I would see 100% would confuse me...I think I'd want a 0%-100% scale per-CPU &/or per-core so I could easily tell when some program has pegged a CPU/core...

It really doesn't make any difference if the tests are run on the same machine. You don't have much control over how multi-processor machines are going to handle the load in most cases...

The main difference is that AutoIt is still actively developed.

These task-automation languages are not meant for large projects or time critical applications, so the speed is not the most important thing. AutoIt’s built in COM support, Unicode handling, data types, arrays, much better flow controls (loops, conditionals, switches), better networking support oppose AHK’s faster operation, simpler hotkey/hotstring definitions, low level hacks, and most importantly, a more helpful user community.

i like AutoIt's versatile functionalities but i hate to see...

1) $ prefix on every single variable name
2) Start...End blocks rather than {...}
3) basic-like operators such as AND OR NOT rather than c-like operators && || !

I disagree.
Although AutoIt is more mature in every other sense then AHK except for speed, I still use AHK just for that reason. Automatition langauges aren't ment for large projects but tendency goes to large number of 10-liner or simple scritps. As either AHK or AU3 can run only 1 script this quickly evaluates to bunch of processes doing very simple tasks in the system. Performance and memory footprint soon becomes a problem, not to mention control and ugly looks in process list. If I don't have multithreading aware automatition lanugage, I can still choose to run multiple processes of the one that is the most friendly when my system is in question.

Add to that that OS generaly runs another 30 processes by default, and another 10 per user, add 10 AU3-s to that waiting for a window or automating cell operation in Excell, and u just made your double core act like 486. And if you happen to run Java or dotNet along .... you got the point.

IMO, every-day tool like AHK should be as fast as possible and as light as possible, and that is for me primary attribute. Otherwise, i would use AU3 from the day 0.

_________________

the scripts above are purely testing the speed of asimple ahk Loop function which is totally different to a while() which evaluates a complex expression (not just a number but could be return of multiple functions)

Other tests you can try

ahk

aut


ahk

aut

... in your first AHK code is not needed, and you can replace the i values in your second AHK code example with A_Index. If you use the SetBatchLines -1 command in the AHK sections, is the AU3 code really faster?

A loop is a loop is a loop, whether you use a simple loop form with options, or a multitude of variations (for/while).

i have never used any of AUTOIT or AHK
i was looking for info in order to decide.
just by reading those guest posts bashing everyone , and asking for more credit i have made my mind alredy.

even that i had never used any of the two, just by simple google searching for info on both i noticed that AHK had some AUTOIT influence, and after just a couple of minutes i even noticed they were credited in many parts.
at one point i even thought they where brother projects (seeing the references of autoit in ahk alone)

then i went to autoit forums and omg!!!!
they dont seem to make them look like brother projects at all

as far as credit goes in GPl or other type of open licenes
if you follow the ruls you are good to go.

i say this as a programmer . users could;nt care less about who made what, they want a usable app period.

programmers on the other hand like to be credited (im ok with that)
but as someone said, it is enough to have a mention in the code that that piece of code was taken from elsewhere and then look the appropiate documentation if you really want to find more about it, i DO NOT like to edit code where half the content is credits 1/4 remarks and the other 1/4 code, that complicates readability a lot
if i am somehow interested in sending flowers to the original , then and only then will i look at the docuemtnation in order to find who he is, what his name is, whre does he live, and what color he likes his flowers.

but since I COULDNT care less either, dont expect any flowers any soon.

better try to make a better product adn then the people who care about credits will start wanting to know about the original coders.

@arana - Nice rant, would you mind explaining what you just said in a way that isn't quite that confusing and disjointed? Most of that seemed to be you getting pissed off about credits/comments in a code that you will probably never even look at.