Lightweight AV update

Comodo Internet Security - CIS Added/Rejected Wishes - CIS
#1

For CIS to be truly lightweight, its AV update process must also be light on memory and CPU usage. Below are many threads where users are very frustrated with CIS’ AV update resource usage and duration. For many, the frustration causes them to uninstall CIS. I suggest that Comodo release 3.14 with this problem fixed instead of waiting a month or more for 4.0.

https://forums.comodo.com/feedbackcommentsannouncementsnews_cis/very_poor_performance_pc_unusable_during_db_updates-t47900.0.html
https://forums.comodo.com/anti_virus_help/virus_update_times_are_excessive-t47520.0.html
https://forums.comodo.com/anti_virus_help/cis_update_huge_lags-t44468.0.html
https://forums.comodo.com/anti_virus_help/how_can_i_disable_an_automatically_updates-t46836.0.html
https://forums.comodo.com/anti_virus_help/comodo_takes_too_long_to_update_on_old_computers-t46099.0.html
https://forums.comodo.com/anti_virus_help/cav_extremely_slow_update_with_very_high_resource_use-t44941.0.html
https://forums.comodo.com/anti_virus_wishlist/better_speed_performance-t46962.0.html
https://forums.comodo.com/anti_virus_help/av_update_only_when_idle-t46969.0.html

Edit: updated CIS version, added another topic link to the top.

#2

Its not something that can be easily changed, CAV’s will probably will have to be made new for this.

#3

I agree that it’s not likely an easy change, but it’s definitely a necessary change…

#4

The update could avoid impacting the CPU resource by having a separate process for the update, with a low/background priority. The update could avoid impacting memory by limiting it memory usage to, say, 10MB. This limit should apply to the total memory (working set plus virtual) to avoid pushing other processes into virtual memory and greatly slowing down the system.

With such limited memory usage, the update will take longer to complete. This creates a problem for how to continue real-time scanning while the update occurs. One way to solve this problem is to maintain two databases. One is used for real-time scanning, and the other is updated. When the update is complete, the AV engine switches which database it uses for real-time scanning. Thus, CIS ping pongs between the two databases.

#5

Yeh… Have separate process and a low CPU priority might be an alternative until things are fixed internally…

#6

Also see this thread on a similar topic:virus update times are excessive.

I know some of you have posted there as well…and I like the concepts you have proposed to remedy this issue.
Whoop

#7

In the opening post, I updated the CIS version and added another topic link to the top of the list.

#8

I agree!

I don’t understand why COMODO uses cmdagente.exe to update database and cfpupdate.exe to update to every new release.

I guess CIS should use other process, called cisupdate.exe, or update.exe, to do all update service, update database and update CIS, and with an option to the user to select the CPU priority usage.