You simply can't add another function without having a system resources overhead.
And who is saying that? You guys.
I'm just saying it is not a resource hog.
It takes less resources than deep scanning.
An on demand scanning of avast takes much much resources than a HIPS tool.
That it is what I'm saying.
Of course it takes resources... All feature or application takes.
It is NOT a resource drag or hog. It's a light, very light, feature.
To sandbox an application requires additional processing power and RAM that otherwise wouldn't be being used.
Of course. We're not saying that. Of course...
Just that on access (auto) sandboxing uses very little resources compared to scanning.
Or, it won't take more resources than just running the program outside of the sandbox... A little, perhaps, but not a resource drag.
How much of a drag that is going to be is dependant on a) the sandboxing software/function, b) how many applications are sandboxed and c) the users system spec.
Sure... How much resources does running a program inside and outside the sandbox will be the difference.
Here I'm saying that the
protection achieved by auto sandoxing is
NOT a resource hog.
On contrary, a lot of on access scanning could take more resources than that.