Not sure if that is a correct statement. However, I notice that scheduled scans take approximately 30% longer than before after upgrading to 88.1.

I'm not complaining, as one of the _*_major_*_ features of this release is the retiring of the use of cygwin1.dll. That in and of itself is a massive improvement, as we use other tools that also use cygwin, and the version incompatiblities were friving me nuts.

I'm just wondering if others are seeing the increase in scan times?

bp

I have experienced a similar problem. My hard drive currently has about 60 GB of data. Doing a full scan of the drive with all the default parameters (i.e. haven't added any additional exclusions) using 0.88 takes approximately 192 minutes. Doing the full scan with 0.88.1 took significantly longer, although I don't know exactly how long. I have the scan set to run over night and in the morning the process was still going (around 7-8 hours after the scan was started), at which point I cancelled it. It was also normal for clamscan.exe to spike up to around 800mb of ram usage while scanning large files (saw it happen when scanning CD image files around 700mb in size).

After adding various file exclusions for video files and cd image files, the scan with 0.88.1 was able to finish in around 338 minutes. Barring the fact that I had to add extra exclusions in order to get 0.88.1 to finish in one night (vs. the default exclusions using 0.88 ) it took approximately 57% longer.

I've read through these forums and haven't found anything that helped. I tried uninstalling and doing a fresh install of 0.88.1 but it didn't seem to help. Because of this I have currently rolled back to using 0.88.

it is strange, my findings are completely opposite. 0.88.1 non-cygwin is slightly faster then 0.88 and uses considerably less CPU. I guess it depends which file types are you scanning. Also note that 0.88 does not scan filenames with nonascii characters, which is a potential threat, so using 0.88 is not a good idea.

It's taking an excessively long time on my PC as well, although I couldn't tell you if the CPU usage increased, since I let ClamWin run overnight each night. The scan begins at 4 AM, and it was usually done by at least 7 AM, because if I woke up that early, it would be done. Now it runs into noon or later.

Let's do some hardware comparisons to see if there is a relation. Here's my computer:

Athlon 64 3200+ (Venice core)
1GB PC3200 DDR (2x512 Samsung chips)
2 Seagate 7200.8 120GB HDDs in RAID-0, 2 partitions of 120GB each (I scan the 1st partition nightly)
DFI Lanparty NF4 Ultra-D Socket 939 board

could you please run a comparative test, I uploaded clamav 0.88.1 cygwin build here:
https://files.clamwin.com/clamwin-0,88.1-cygwin-setup.exe

You need to uninstall clamwin 0.88.1 and the install the cygwin version and then run the same scan as before and note the time it takes.


It would be interesting to see how the same code compares built with cygwin and native win32.

Thanks

I pulled the scan summaries for the last three 0.88 scans that were run on my system as well as the last few 88.1 runs.

I notice a couple of things. First, to be fair, it does look like 88.1 scans more stuff. Note that the amount of data scanned in the first 88.1 scan jumped from the previous 88 scan by 110 MB. However, much of the transient data went away, and more recent scans are with a similar data size as before.

But, if you take the amount of data and divide by the time, you can see that 88 scanned about 55-57 MB of data per minute. 88.1 seems to be running about 45-46 MB per minute.

This is on an AMD Sempron 2800+, with 1GB memory, Western Digital WD400BB-00GFA0, Windows XP Pro SP2.

I won't have time to run the cygwin build until sometime tomorrow (4/26).

bp

Another set of logs from a different system. This is an older P4 Windows XP home, running at 450 MHz, and memory limited at 382 MB. However, the results are similar. With 88, it was able to scan 43-44 MB/minute. With 88.1 it is doing 28-33 MB/minute. Here is a selection of summaries with MB/minute annotated right after the scan time:

What do I do with the files in the zip?

It was my mistake, the correct URL is:
https://files.clamwin.com/clamwin-0,88.1-cygwin-setup.exe

Most definitely using more CPU. It ran all night and did not finish what is normally a 2 hour scan in the previous version. Then when I cancelled, my pc was dogged, I had to revert to the previous version to work.

would you please read the above posts, try the suggestions and post your results and computer configuration?

I made some adjustments that should hopefully address the cpu usage issue. Please download test thoroughly ands post back the reults. The beta is here:

https://files.clamwin.com/clamwin-0.88.1.2-setup.exe
Thanks

Here's some tests i just did :

I set up a directory holding (amond onthers) my download and projects folders, which are mixed type of archives, exe's and text files. The PC I'm using is an Intel Celeron 800 MHz clone running Windows 2003 Server.
The folder I scanned holds 1,49 GB in 9175 files, 1627 folders.

First I tried the most recent 0.88.1 without cygwin, which was already installed.
I used the following settings :
- Scan in Subdirs (off course)
- Display Infected Files Only
- I turned off all default filters to maximize the amount of scanned files
- Do not scan archives > 100 MB (default is 10)
- Do not extract more than 500 files
- Do not extract more than 5 sub-archives
- Treat files as mailboxes
- extract attachments & macro's from MS Office Docs
- Detect broken executables
- Scanner priority : Normal (I think default is Low)

The report for 0.88.1 gave me following results : 9064 scanned files, 2733.88 MB, in 72 minutes an 46 seconds.

I repeated the test with the same settings (except for Detect broken exe's which wasn't there) in 0.88.1 with cygwin support. The report shows 9064 scanned files, 2532.96 MB, in 65 minutes and 21 secs.

ClamWin 0.88 with the same settings gives about the same results : 9064 files, 2529.90 MB, in 67 minutes 26 secs.

To rule out the Detect broken exe's option was causing this, I repeated the test with 0.88.1 without cygwin, after put of this option. Now the results are 9064 files in 2733.88 MB, 73 minutes and 32 seconds (which is even more than with the option on).

Conclusions : there are no sensational differences, but still the new native version seems to take about 10% longer.

Greetings,
Budtse

Thanks,


please benchmark the new one:
https://files.clamwin.com/clamwin-0.88.1.2-setup.exe

Also to eliminate windows file cache interference, please reboot the computer between tests

OK, just ran 0.88.1.2 with the same settings as above (including detection of broken exe's).

This one scanned the 9064 files (2733.88 MB) in 68 minutes and 15 seconds. This is getting very close to the 0.88 version.

Great work!