This is amazing compared to MS Security Essentials' 200mb @ idle (dont even start to scan).
Vipre - 7mb ram @ idle
Wednesday, June 1, 2011
Subscribe to:
Post Comments (Atom)
This is amazing compared to MS Security Essentials' 200mb @ idle (dont even start to scan).
Vipre - 7mb ram @ idle
Interesting. Though I don't understand how you got the 200mb idle? Unless, it was busy working, updating or doing some kinda of internal Microsoft churning. As I type this, my computer is showing MSSE (up-to-date)running at a mere 5,148K, coupled with COMODO Internet security (firewall only) at 3,464K...doesn't seem like MSSE is hogging much RAM. Even with a COMODO combination, it's still less then 13,778K. Wish I could upload a task screen shot.
ReplyDeleteHey Peter, thanks for your input, I am actually getting mixed responses from others, some saying that 200mb is unusually high (i agree 100%), and some tell me their system is *only* showing 100mb usage at idle - I feel that anything over 50mb at idle is not acceptable. I have probably deployed over 200 copies of msse, many of which have recently shown anywhere from 10-150mb ram usage after just sitting for 5 minutes, not touching the mouse, all programs closed - what gives?? msse clearly shows when its doing a scan, and clearly shows when its doing an update, but when i check these machines, it reports that it is doing neither, obviously when you launch a new app, or open a file, theres an initial active scan activity. At any rate, I have had extremely poor detection rates from MSSE and ESET NOD32 over the last 2 months, especially from google image searches, several upset clients called with viruses - no longer my favorites.
ReplyDelete