Why back when I posted a problem I was having that seemed to involve cmdagent.exe.
Periodically my hard drive light would come on unexpectedly and my system would become sluggish. During this time I am able to bring up Task Manager and cmdagent was seen gobbling up CPU cycles.
When the disk light went off the CPU percentage was about 30 or so. It would then continue up until it hit 56%. Then it returned to it’s usual 0%.
In trying to nail down the possible cause I disabled things one at a time and ran like that for a few days. Disabling Component Monitoring finally resulted in my not getting this strange behavior. I’ve been running without it for over a week and I have not once had this problem.
So what do you make of this? Could it be when CM is enabled I am doing some sort of excesssive paging? I do not nor have I ever seen this sort of behavior with any other software on my system.
Using the latest version of CPF. XP Pro SP2 with all hotfixes. AVG Pro. 1GB RAM. with a 2GB Page file on a separate hard drive.
Hi, from what I can see, it may not be CM perse, but something it is monitoring that may be taking up more time or conflicting. Just a thought, if it is monitoring AVG, there may be some issues going on. Did you have it in Learn Mode or just ON prior to this? I do have other securities that when going through a monitoring stage\updating stage would spike my usage and then finally drop it and isn’t the first time i’ve seen or heard of this aside from Comodo. I would try in learn mode first and see if this happens. Another note,when MS first suggested moving the page file to another drive to speed things up, this actually resulted in higher usage and worse performance, way to go MS. I would also try moving the pagefile back to main drive.
One reason my page file is on another drive is so I can defrag my system drive within Windows. Having the page file on it would require me to do a boot time defrag as the defraggers can’t lock the partition with an active page file on it.
And I have had no problems with where it is located. I really don’t think it’s placement is the problem unless the problem is caused directly by CPF and it has a problem with my page file on another drive. ???
I also at one time excluded CPF from AVG’s resident shield processing to no avail.
Could the CM list be getting whacked out or be so big that it would cause excessive paging and CPU utilization? I did do uninstalls/reinstalls which should have started things from scratch.
Any thoughts from the developers of CPF? You know it’s ins and outs.
I did some research into the placement of the page file. It’s not a good idea to place it on a different partition on the same physical drive as your system partition. However, I saw nothing negative about it’s placement on another physical drive as I have done. At the worst it won’t improve performance but it doesn’t appear to hurt it either. FWIW.
Also… I only started getting this behavior when I went to v2.3. The previous version never did this. My page file has been where it is for a very long time.
Well I ill worded my last reply about pagefile. I can’t find the article now right from MS though that stated a lower performance when moving page file, and it was referenced to overwrite the moving it to another drive supposedly increases performance, many will leave it on the main drive as it works for them.
Many partition softwares will throw in about moving page file to another drive with ease of their software and improved performance etc… in order to sell it. If I find it i’ll post it but my point I was making as far as moving it was mainly due to a bad page file. Try moving it to main, if it works then you know. Another issue due to this is because some drives operate slower and the page file on a separate drive may not be able to keep up with the main drive. It sounds as if you have two of the same speed drives, correct?
I know of the issue of defragging with moved page file but there are numerous arguments about defragging NTFS to begin with, some say you don't have to, some move page file to do so, some download products to do this, some don't care. I find it defrags just fine either way and the noticablility is so slight anyway, many of us mortals won't notice. ;)
I don’ t know why you would have to do a boot time defrag, I have the same OS and don’t need to do a boot time defrag. This is an option, not a “have to”. I always have my pagefile on my main drive partition and always have defragged so if this is the case for you, you have other issues with your drive\PC. As I stated, either move it, or create\delete the old, remake\move another on same drive as current or OS drive and see what happens. Especially since this just started, i’m guessing a hard drive\and \or pagefile issue but not ruling out CPF yet.
I am convinced it has nothing to do with my page file nor with it’s placement. I did turn CM on yesterday for the first time in more then a week. Within 1/2 hour the problem occurred. Keep in mind that I only suggested paging might be what is causing the unexpected disk activity. What explains the high CPU utilization of cmdagent?
So for now I will just leave CM disabled and be done with it. I would not be the least bit surprised if the next version of CPF ‘fixes’ this problem even though no official word has come down that my problem is recognized by Comodo.
It may very well be CPF then. There were other issues with this but haven’t seen this one specifically. I still think it’s possible it may have to do with an application it’s scanning though, or is getting stuck on something. Are all set to allow? Check that to make sure. In learn mode they should be. It may be something else installed conflicting with CPF. Did you do a reinstall of CPF in auto mode?
Also, I was curious as to why you have to do a boot defrag. You shouldn’t have to.