Search the Community
Showing results for tags 'ssd'.
When running benchmarks on my 960 pro with internet security 18.104.22.168 enabled the performance is drastically reduced?. Paused protection = 2,224Mb/s read and 1,970 write. Enabled protection = 598Mb/s read and 1,122 write. I searched the forum for others with this issue and found a post from 2016 that was closed, people also reporting this loss of speed using SSD with Eset. In the post you hint at it being only the benchmarker being to fault. can someone tell me if this is true. Samsung magician latest version. thanks for your time in advance.
I've latest regularly updated ESS 10 installed and running on a Win10 64-bit PC. Looking at Process Explorer, it writes to system SSD about 3-4GB/day, but reads back only 1-1.5GB/day. An obvious question is, what exactly ESS writes to disk? Why it reads less than writes? Can such writes be done into RAM instead of SSD to prevent the SSD wear for no valid reason? To add some info, I've PerfectDisk defrag running in "prevent fragmentation" mode. Also ongoing LAN traffic from security cams, which is not saved to disk by CAM software, but processed in RAM to detect motion. Also web browsers - usually around 500MB/day sessions saved, and internet video streaming via browsers. I wonder, may be Eset Real Time Protection catches the video streaming, which portions are temp saved to browser cache on disk, and then later deleted and replaced by the next video fragments? But why Eset needs to write so much data to SSD on ongoing basis, when no threats are usually identified by disk scans or RTP? My goal is to completely stop Eset writing to SSD unless a threat is found and needs to be saved locally. How to do that? How to find out exactly, what data Eset keeps writing to disk? If I can't do it on my end, I ask the Eset devs to move all web fragment analysis to RAM instead of constantly writing to be analyzed data to disk, and then replacing it on disk with the next data. I didn't subscribe to Eset to kill my SSD, this is the wrong way to dynamically analyze received from network data.