Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Video Reviews - Security and Privacy
Kaspersky Antivirus 2017 System Watcher Test (Impressive results!)
Message
<blockquote data-quote="RejZoR" data-source="post: 577616" data-attributes="member: 57233"><p>I disagree. If you look at the report, performance figures are in line with everyone else. Only time it has a performance hit is during installation/uninstallation of apps and launching of apps. My guess would be, the reason for this is System Watcher. Those are the scenarios when System Watcher has to monitor a lot of things for their potentially malicious behavior, creating performance hit. Considering the efficiency of it, I'd say it's a performance hit I'd be willing to forgive any time. These two scenarios also usually mean recognition of yet unknown new files before caching mechanisms kick in. Meaning, you won't even see this performance hit once file has been considered as clean and cached by those mechanisms. It's how avast! always scored rather poorly in performance tests for new files and yet on my system it has been one of the lightest AV's of all times.</p></blockquote><p></p>
[QUOTE="RejZoR, post: 577616, member: 57233"] I disagree. If you look at the report, performance figures are in line with everyone else. Only time it has a performance hit is during installation/uninstallation of apps and launching of apps. My guess would be, the reason for this is System Watcher. Those are the scenarios when System Watcher has to monitor a lot of things for their potentially malicious behavior, creating performance hit. Considering the efficiency of it, I'd say it's a performance hit I'd be willing to forgive any time. These two scenarios also usually mean recognition of yet unknown new files before caching mechanisms kick in. Meaning, you won't even see this performance hit once file has been considered as clean and cached by those mechanisms. It's how avast! always scored rather poorly in performance tests for new files and yet on my system it has been one of the lightest AV's of all times. [/QUOTE]
Insert quotes…
Verification
Post reply
Top