jackuars

Level 24
Verified
I recently installed KSC Free, the first few days, I didn't feel any performance issues and it consumed very little memory 60-70MB in the background. It felt lighter than ESET in terms of RAM consumption, but as soon as I started using a resource intensive program such as Tableau the performance came to a crawl. I have an Intel i5 laptop, Intel HD 5500 with 8GB RAM, I run very few programs in the background.

I know that RAM consumption is not an indicator of performance, but the values showing in Task manager doesn't match with what's showing on Process Explorer by Sysinternals, are they deliberately showing lower values in Task manager?

 

stefanos

Level 28
Verified
I recently installed KSC Free, the first few days, I didn't feel any performance issues and it consumed very little memory 60-70MB in the background. It felt lighter than ESET in terms of RAM consumption, but as soon as I started using a resource intensive program such as Tableau the performance came to a crawl. I have an Intel i5 laptop, Intel HD 5500 with 8GB RAM, I run very few programs in the background.

I know that RAM consumption is not an indicator of performance, but the values showing in Task manager doesn't match with what's showing on Process Explorer by Sysinternals, are they deliberately showing lower values in Task manager?

The problem with your system is that it uses too much ram. It's definitely not from Kaspersky. Try this on your windows. Tutorial - How to slim Windows 10 and make it superfast And this
 

Local Host

Level 21
Verified
Could be from the behaviour blocker, due to suspicious tasks from Tableau, other than that Kaspersky is only heavy when disinfecting malware.
Kaspersky use many private bytes
Hardly the likes of F-Secure have +400MB, plus that is reserved memory anyway, is not being used.
The Private Bytes counter indicates the total amount of memory that a process has allocated, not including memory shared with other processes.
That why it's called Private Bytes, if you guys wanna check on how much RAM a process is using WS Private Bytes is the most accurate metric (it shows what memory that process alone is using).

The Working Set shows shared memory usage, which will duplicate values like avp.exe already takes into account the avpui.exe values and probably other processes (is not showing the values of the avp.exe alone).
 
Last edited:
Top