How Efficient is AutoIT

[condoman]

I have a backup scheme that uses BAT files to copy files from one drive to another as a means of backing up. If I use AutoIT to accomplish this is it more or less efficient or does not matter? The files are 10-15 gig in size.

[water]

If you just do a FileCopy I think you won't see a difference.

[condoman]

FYI.

11.6 G file; AutoIT 15 seconds slower than BAT process, guess it does not matter.

[guinness]

With all due respect you haven't provided any code so your results mean nothing.

[condoman]

I'm sorry, I did not think I needed to supply source for: 1) log time, 2) copy file, 3) log time. I saved it and will provide if you wish.

My question was more to see if there was a huge difference in copying a file, it appears to me there is not.

Thanks

[guinness]

It would be polite.

[James]

More efficient than you would be at copying those files by hand

[Xenobiologist]

You can try to automate tools like this : http://www.chip.de/downloads/FastCopy-64-Bit_44420604.html

[TheSaint]

@condoman - I know this is not what you asked, but I suggest you look at a more efficient and safer way to back up you files, using md5 etc.

In fact, there are many good backup programs out there, that will do all you want .... many of them free.

If you want something that is quick and simple, then I recommend TeraCopy big time. I move/copy a lot of big files around often, and it gives me peace of mind. Integrates with Explorer to make it even more seamless. I only have it partially integrated and use it via right-click drag and drop. Has to the most brilliant third party program I've ever come across to use with Windows. It comes in two flavors - Free (which I happily use) and Paid (Pro version) which most don't need.

[JLogan3o13]

I'm sorry, I did not think I needed to supply source for: 1) log time, 2) copy file, 3) log time. I saved it and will provide if you wish.

My question was more to see if there was a huge difference in copying a file, it appears to me there is not.

Thanks

I would agree wholeheartedly with guiness: how you are doing a file copy will help determine if the inefficiency is with AutoIt or with you. For example this method of copying 1000 files:

FileCopy(@DesktopDir & "\Test1\*.txt", @DesktopDir & "\Test2\*.txt")

requires a different length of time than this method:

#include <File.au3>

Local $aArray = _FileListToArray(@DesktopDir & "\Test1", "*.txt")

 For $i = 1 To $aArray[0]
  FileCopy(@DesktopDir & "\Test1\" & $aArray[$i], @DesktopDir & "\Test2\" & $aArray[$i])
 Next

And there are a myriad of other ways to go about it as well. Without showing your code, you're asking us to first guess at how you're doing it, and then troubleshoot why it is slow. Help us help you

[numdig]

Has to the most brilliant third party program I've ever come across to use with Windows.

.

So I guess you haven't come across Robocopy then. Robocopy, the joy light and hapiness of one's life. Robust to network disruptions, mirroring, handles long paths even when ms-dos copy doesn't, patterns, includes/excludes, properties timstamps, FAT disk timestamp precision issues, tee-style logging (to file AND to console), dry run/list-only. All for free originally in the win srv 2008 tools package. After so many years I still keep discovering new uses options and features. (sigh) (love)... I ll still check yours to see if I'm not missing on sth, but I doubt. Take care. P.

[TheSaint]

So I guess you haven't come across Robocopy then. Robocopy, the joy light and hapiness of one's life. Robust to network disruptions, mirroring, handles long paths even when ms-dos copy doesn't, patterns, includes/excludes, properties timstamps, FAT disk timestamp precision issues, tee-style logging (to file AND to console), dry run/list-only. All for free originally in the win srv 2008 tools package. After so many years I still keep discovering new uses options and features. (sigh) (love)... I ll still check yours to see if I'm not missing on sth, but I doubt. Take care. P.

Yes I have, and last time I used it, it was way outside the same league as TeraCopy, as regards a Windows copy/move replacement.

With TeraCopy, you get md5 checking and you can do comparisons, and best of all, you can queue up jobs from various locations to various destinations .... and even add to existing jobs. The process even continues to work when individual elements fail, and doesn't spit the dummy (like Windows does) at a bad copy etc, just reports every instance when finished, and you get the ability to try again for just those files. You get even more with the paid for Pro version. My memory of RoboCopy, is that it is a very different kind of fish and much more complex.

TeraCopy can be as seamless as you like it too - either fully replacing the regular Windows processes, or like I use it, via right-click and/or copy and drag ... which is brilliant, as I can still use the regular Windows processes for small stuff if I so wish.

In fact, I recall hearing or reading somewhere, that Microsoft were interested in the product ... it's that good.

EDIT

When copying/moving lots of files and/or big files (especially) around, I've known Windows to fail and not advise. Generally you don't realize this until a later date, when you come across 0 byte files. This is usually from one harddrive to another, and appears to be a memory related issue regarding indexing. This happens with TeraCopy too in the same circumstances, but the difference, is that it gets reported and you can see immediately what elements failed and can very simply select just them in the GUI to try again and again and again, until they all succeed. This happens on some PC's more than others, and most people are unaware of the Windows failures, until it is too late (years hence). If you think it hasn't happened to you, then I'm sorry, but I have some bad news for you.

I'm lucky, because I always keep multiple copies of my files on different drives/discs/etc.

In fact, I only became aware of the problem, when I decided to relocate some stuff years later, using CDCheck (works with disc and drive folders) to make sure all copied ok.

I rarely use CDCheck now, because TeraCopy is that good.

Once I realized there was an issue, and until I came across TeraCopy, I had to double and triple check every important Copy and Move I did ... for years. Being aware of the issue, and checking, I also discovered how often (to my disgust) the errors occur, without notification.

TeraCopy has been a brilliant step forward and gives me peace of mind.

EDIT 2

I've wondered for decades, why many of the features available now with TeraCopy, weren't standard abilities in the regular Windows' processes. I could never understand why Microsoft never improved something, that we use many times a day, that was so hugely lacking.

EDIT 3

TeraCopy also has a command-line ability, which I regularly use in scripted automation.

Edited May 3, 2013 by TheSaint