This is no bug report or asking for help. Its a topic to discuss the performance of the antivirus.
(Last line of defense, but biggest eater at table).
I just took comodo antivirus for a moment again. But any good will went away after i saw the cmdagent taking cpu of, lets say “50%”, each time i open firefox, or other programs.
Not to mention that it has been on statefull. And updates have been “sheduled to once a day with the workaround”.
Its even too much using of cpu for a first scan, and comodo is with statefull inspection much more cpu using than another antivirus without statefull inspection would be in the first run.
When i use my old antivirus, like now, i can open firefox as often as i want, the spike of its guard is like 1.5% cpu using, and very seldom. I tried it right after i re-installed it again after the comodo “test”. And it has anyway no statefull mode at all.
The statefull inspection of comodo looks like a feature, but in fact, its like a patch against maybe more cpu wasting otherwise. While on statefull it tops allready all negative expectations, … by far.
Sometimes it can be the first line for the user.
For comodo its the third line. This makes it so paradox. “For useabillity only”, but hogging the cpu.
I never understood the campaign against antivirus. I never had a problem with my antivirus.
But when i install comodo antivirus, i want to disable it and trust in the defense+ … if i had not to cover up new entry files with a scan first.
I got a similar complaint from a user today. These pics were taken 29 and 16 seconds apart, on an Athlon XP PC running XP SP3 while opening a database application. Subjectively, previous AV went nowhere near 90% CPU and didn’t take as long. If I get time I should be able to try it with the old AV from a backup HD tomorrow to compare.
I suspect cloud issues here, indeed it shouldn’t (AV) rescan if in stateful and no DB update, but I’m afraid the cloud code is part of D+
Also command-line analysis can have impact because of the trail of files that are opened if FF starts.
Can someone fiddle around with D+ scan cloud etc settings to see if it leaves the CPU alone at repeated start-ups of FF?
Reloaded backup image including previous AV which happens to be Avast 6.
The difference is stark.
I tried starting Firefox, first with Avast caching turned off, and actually had a bit of trouble getting screenshots of CPU activity during the short time it was happening. (see first 2 attached).
With caching turned on, starting FF for the first time there was a relatively long spike of high CPU activity on opening and a little on closing too, but on following occasions there was no apparent AVASTSVC.EXE activity.
Now back to CIS set to ‘Stateful’, every time I start FF, CMDAGENT.EXE gets quite excited for long enough to easily take a sequence of pics of a selected area of screen (3 pics attached).
I don’t understand what it is working on if it doesn’t have to check FF again and again.
If the antivirus part of comodo is uninstalled, all is back to normal.
Cloud wasnt enabled.
An antivirus should not use that much cpu in any way or moment. In fact, i installed comodo to benefit from the statefull. Got opposite effect.
Now i installed avira, and in the magazine description it said: Unfortunately avira doesnt care if it scanned a file before.
But what to say, it runs “50 times” better (seldom 1% cpu useage compared to about 50% of comodo in statefull), even if avira misses to have this feature at all.