Another test run - same PC’s as before but copying 120 files, all .jpg varying from about 1.5MB up to 3.5MB for a total of 265MB. All from one source folder to one existing destination folder, done on a “Select all, copy, paste”.
Both PC’s rebooted, Avast “All Active protection stopped” on both - Copy/paste took 35.87 seconds.
Files in Destination folder deleted, both PC’s rebooted, Avast “All Active protection stopped” on destination PC only - Copy/paste took 37.23 seconds
Files in Destination folder deleted, both PC’s rebooted, Avast active on both - Copy/paste took 45.17 seconds.
A further two copy/pastes were then made after deleting the files in the destination folder, but not rebooting either PC, with Avast active on both PC’s - Copy/paste took 39.1 and 38 seconds.
Additional observation. On the source PC, after rebooting and with Avast active, the “a” ball was spinning during the the copy paste operation, as was the “a” ball on the destination PC. On subsequent copy/paste’s where the source PC was not rebooted, the “a” ball was stationary on the source PC during the operations. Is Avast keeping track of which files have been previously scanned on open?
Interesting i haven’t noticed this before but i gave it a shot when i read this thread and copying a 2GB folder full of smaller .jpg files over my LAN network it is quite obvious avast! IS slowing it down. With around 6-7 MB/s with avast! on and after i pause the standard shield it goes over 10MB/s.
EDIT: Forgot to mention i am running Vista 32bit here.
In relation to the double scan (scanning of the files on the source PC by the Avast on the destination PC, as well as being scanned again on the destination PC) that you are experiencing, you could try excluding the source PC from being scanned by the destination PC.
In the Standard Shield, Customise, Advanced, enter the source PC path in the form \SourcePCname* in the list of locations that will not be scanned.
Could you please try this and let me know whether it makes any difference.
Olddog- Now we are getting someplace. ;D Hopefully devs will notice this thread.
Tests (4) Copy and paste directory with 51 jpgs(2-5MB) totaling 182MB from one networked laptop to another.
With Avast standard shield paused on TGT computer = 2.46MB/sec
With Avast standard shield active with exclusion for “\SRCcomp*” = 2.14MB/sec
With Avast standard shield active with no exclusions = 0.99MB/sec :o
With Avast standard shield active with exclusion for “\SRCcomp*” = 2.3MB/sec (Same as number 2 to confirm findings)
All tests were done consecutively without rebooting running Avast 4.8.1229 under Vista 32 Ultimate. It looks like the scanning of the src files prior to copying under Vista is slowing down the copy process. Odd that this doesn’t happen under XP.
I noticed during my tests that when I first used Explorer on the destination PC to find and open the folder on the source PC, the files do appear to be scanned as they a displayed on the destination PC screen. It is after this that I started the copy test, using the “select all, then copy” and no further scan occurred at that time. The only scan that occured once the “paste” was issued was to this files being written into the destination folder.
So perhaps what you are referring to is occurring on XP, but at a different time in the process. Again though I am fairly sure the initial scan above only occurs once and not on subsequent runs done without rebooting. I’ll try to get some more tests done tomorrow to confirm this and post back the results
Interesting on the timing issue. When I do a copy and paste, I copy the directory so maybe there isn’t the opportunity for avast to scan the files prior to copy. It just seems silly to scan the file on the src then again on the tgt when copying.
I really don’t like the idea of excluding all the files on the remote computer as a solution. Hopefully the devs will see this and at least respond if that is my only solution. Thanks for all your help. This is a great forum because of its contributing members. I’m sure the developers really appreciate the testing.
It makes quite a big difference what is being copied. In particular, files like JPEG, DOC, XLS are scanned “on open” (when you read them) - most other files are not. So, if you copy this type of files, the source is scanned before the requesting program gets the data.
If you already access the source files (which may be e.g. just by opening the folder in Explorer - and Explorer scanning the files to display thumbnails) and avast! scans them, it remembers their status - and unless you modify them, avast! will not scan them again (cause it knows they are clean)
You know that you are copying the files - but avast! does not. For avast!, it’s just an application (Explorer, for example) reading some files and writing other ones; there’s no way to tell if the written data are the same as the read data - they may have been modified by the application, or they may not be related at all.
I don’t know, however, why JPEG files should be scanned when written - unless either the sensitiviry of the Standard Shield is set to high (specifically, it’s configured to scan all created/modified files), or some other application (could be Explorer again, scanning for thumbnails on the target side) is reading them as they are created.
Igor - For my setup, it is jpg and I am set to normal for standard shield and it is definitely scanning twice when copying a directory.
Interesting on the “already accessed issue”, because I copied the same directory from the source computer 4 times without rebooting and the files were not modified at the source, but yet it rescanned them when not excluded. It does seem that XP is not rescanning them based on other user’s post.
Thank you for your advice. It explains most of what has occurred during the tests I ran.
You said
[QUOTE]… I don’t know, however, why JPEG files should be scanned when written - unless either the sensitiviry of the Standard Shield is set to high
[/quote]
I do have the sensitivity of my Standard Shield set to High - Out of interest I will try the same tests again with it set to Normal
OldDog-On your XP, High is the same as normal on Vista. So essentially there is no normal on Vista, just high with regards to this. I would prefer the option of only having Avast on Vista scan the same unchanged file only once during the copy, just like normal on XP.
The Standard Shield sensitivity settings should be the same as they should be independent of OS they are the same be it on Win9x through Vista, see image.
Yes they look the same, but if on XP (according to OldDog) avast only scans the src and tgt under High vs. only scanning the src under normal, then Vista’s normal setting behaves the same as XP’s high setting by scanning both during a copy. This isn’t a visual issue it is a code execution issue.
I don’t think there is any essential difference in how avast acts between the two OSes with the same sensitivity settings.
I would say it is possibly something that Igor or Vlk said in an earlier post about how Vista acts when you open a folder, e.g. trying to access the icon in the file, etc.
I think what Stuck@home meant is that his Normal setting is acting the same in Vista as the High setting is acting on my XP.
Stuck@home,
As a last thought, could you set your Standard Shield on Low, then click on Customise, then select the Scanner(advanced) tab. The radio button in the Scan Created/Modified files should be on “Only Files with selected extensions” and not on “All files”. (On High, this should be reversed). If this is not toggling correctly on your installation, or on Vista, then it would explain the problem.
I don’t have XP to compare, but according to Igor and confirmed by olddog, XP scans the src and tgt when copying on High, but not on normal. Vista as I stated earlier scans the src and tgt when copying on normal.
Olddog- I don’t have an option for Low. Under normal it is set to scan only files with selected extensions. It toggles it the other way when set to high. But interestingly, the extension list under scan created/modified files does not contain jpg’s, so I don’t know why it is scanning them when copied.
Apologies - where I said Low, I should have said Normal. I have Normal/High/Custom. OK, one last thing. If you untick the “Scan Created/Modified files” then it definitely shouldn’t scan them, and if you also go to the advanced tab and select “Show detailed info on performed action”, you might be able to see exactly what it is scanning.
With the scan created/modified setting unchecked it stil scans every file twice. Once on the \tgtcomp and once on the \Srccomp. You can see the files listed on the on-access scanner message. I don’t need to reboot for these setting changes do I?
No you shouldn’t have to reboot. If it is showing that the .jpg files themselves are being scanned during creation (write) on the destination PC with these settings, then I think there is probably nothing we can do at our level to take this further. I would hope that perhaps either Igor or Vic could look into this further to clarify just what it is scanning during the write process in Vista.
