It’s really annoying that CIS doesn’t offer any useful method for restricting when it does its daily updates (like virus files but not 100% sure).
When this kicks off, it jumps my CPU to 70% utilization, forcing my fans to turn on and making an annoying racket. So I immediately open task manager and cancel the update. It can run some other time when I am not at the computer. Although my system is a few years old, it is running an I7 4700K with 16GB ram and is no slouch. So what exactly is Comodo doing to drive the CPU from an average 4% normal usage to 70% suddenly and which will last for at least 10 minutes, perhaps more?
After all these years with essentially the same UI, one would think that someone at Comodo would have had the bright idea to put a time control on updates, say only update between 3-5am daily. But noooooooooooooo.
There is a setting that states "Do not check for updates if I am using “these connections”, which when clicked, opens up a box showing Ethernet.
This is the ONLY choice! There is no apparent way to enter anything else. And in fact, I don’t even know what this means. What does “using Ethernet mean”? That there is an active network transfer going on? That won’t happen when I am merely reading cached stuff.
How do yo figure it is an update and not a full scan being run? How come you don’t run resource monitor and view the disk activity of the process that is using the most CPU and read/write bytes? Sounds to mean it is some kind of schedule system scan or the real time scanning caused by another application accessing a large amount of files, which in turn cause the real time AV to scan those files.
I don’t know it was a scan or not. Which is why I was posing the question here!
So I looked at the AV and drilled into the archaic UI (hint: You have to click the checkbox next to the scan name and then the edit button at the top to be able to see the options and schedule menus). It is possible that this was a scan, which was a full scan, which was scheduled weekly at 11:59pm, which would be in the time range for what I was experiencing. I’ve change that to earlier the next morning and changed a full scan to once/month.
Still, is it normal on other people’s systems for a full scan to run for 45 minutes (or possibly more)? I’ve probably got less than 1.5TB of total data.
I’d say it’s quite a good time for that amount of data. Last time I ran one, it went into a couple of hours although admittedly on several drives. You can also ‘Send it to Background’ which is supposed to reduce resource usage, although taking longer
I have a fairly fast machine with plenty of RAM. And this was across multiple drives. However, I did set priority into the background.
It doesn’t explain why such a huge number of read faults. That is NOT NORMAL.
How can I find out what Comodo is doing here? Assume it is a scan, there should be a log/report somewhere that tells how many files were scanned, sizes, time and a whole lot more. Are Event log records cut for this?
The Scan screen itself when completed shows you what was scanned and the results with numbers & times etc. You can dictate what, when, how and the actions you want if anything is found, but no additional log is kept
I believe I have solved this problem. I run 16GB of memory on this system and I have the page/swap files on a different device from where the OS is. I noticed that I had the page file set for a 4GB size. I changed that to 16GB and the problem seems to have disappeared.