> are you seeing an actual problem with the computer not being responsive or slow to react to user input?
> Or are you just annoyed at the "numbers" you are seeing?
That's avoiding the OP's point. And MrSmite's.
e-claus:
> During 1 hour 15 minutes (= 4500 seconds) the program has managed 704,000 I/O reads (156 reads/sec)
> and 236,000 I/O writes (= 52 writes/sec).
MrSmite:
> in the 30 seconds it took me to write this post I had 36,966 "events" listed in ProcessMonitor.
e-c and MS, check two things. You just need to be sure,
1) that NIS is not doing an idle scan. If you leave ProcessExplorer running/open you would see ccsvchst.exe activity, plus a pop-up from NIS.
2) that it's not running defrag [shakes head].
Settings -> Miscellaneous Settings -> Idle Time Optimizer -> Off
I suppose there is also a 3). You need to be certain that it isn't doing something that is really necessary. With ProcessExplorer look at all the processes that are running and see if there is anything there that looks peculiar.
MAH:
> I am interested in knowing what precisely NIS is doing during those read/write instances,
> so I can make an intelligent decision as to whether I want those to continue.
That's a fair question. I hope someone from Symantec will answer it.
AM's point (of asking that question) is correct on a _relative_ basis. The current NIS is _far_ from the resource hog that it once was. I left it behind for a competitor years ago for that reason. I returned a year or two ago after reading reviews that said that it was no longer true. They were right. Well, again, at least on a relative basis. But even on an absolute basis I don't "sense" NIS running on any of the three computers that we have it on.
I have Microsoft Security Essentials (which reviews well for anti-malware protection) on one of our computers, but you can _really_ tell that it is running. Worse than the old years-ago versions of Norton ever were. And this is the new v. 2 MSE.
On the one hand:
Few people post in this forum about NIS using too much resources. You should explore further to see if you have something going on on your computer that is causing this.
On the other hand:
No product is perfect. There is no excuse for NIS to be doing anything that is not _directly_ needed to protect the computer. A (bad) example of that is defrag. So ... there could be other things like that going on. Or a bug.