catalin 0 Posted October 28, 2014 Share Posted October 28, 2014 Hi, Latest version installed here. ( 6.0.14.0 on rBMP mid 2012) When doing Update a cpu goes in 100% usage. Regards, Catalin Link to comment Share on other sites More sharing options...
Most Valued Members planet 232 Posted October 28, 2014 Most Valued Members Share Posted October 28, 2014 Hi Catalin, That's strange, I'm not able to reproduce this while downloading updates. I was able to see the CPU get to 100% only when it was installing the updates for a few seconds, which is expected. Do you experience any issues when downloading or installing updates? Does the CPU gets that high for a short period of time for installing, or also downloading? Does it continue to happen after restarting your Mac? Are you using regular or pre-release updates? Link to comment Share on other sites More sharing options...
catalin 0 Posted October 28, 2014 Author Share Posted October 28, 2014 Hi, It's happen during update process ether is checking, downloading or installing. In my case no update found. CPU stay at 100% until update (checking, downloading or installing) is finished. I've restarted and even did a fresh 10.10 install. Same behaviour. No pre-release just regular updates. Link to comment Share on other sites More sharing options...
Most Valued Members planet 232 Posted October 29, 2014 Most Valued Members Share Posted October 29, 2014 (edited) Oh, you are right - as soon as it begun checking for updates the CPU zoomed up to 100% until it was finished. Don't know why it didn't do that the first time I tested it. Edited December 17, 2014 by planet Link to comment Share on other sites More sharing options...
Arakasi 549 Posted November 2, 2014 Share Posted November 2, 2014 You would think during updates, either network would be high, or disk activity. However if updates are sent compressed and decompressed in any way, the cpu would be used for decompression, with moving using disk activity. Can eset confirm an issue with cpu priority for updates? Can it be adjusted ? Link to comment Share on other sites More sharing options...
Most Valued Members planet 232 Posted November 6, 2014 Most Valued Members Share Posted November 6, 2014 You would think during updates, either network would be high, or disk activity. However if updates are sent compressed and decompressed in any way, the cpu would be used for decompression, with moving using disk activity. You might be right. It's interesting because the CPU for esets_daemon shoots up the instant it gets to the 'update.ver' part (see screenshot in previous post), but if you try to update offline, it just shows 'Connecting...' for about five minutes but with no CPU difference (stays very low). However looking at disk activity (and memory usage), esets_daemon barely did anything if there's isn't an update available even though the CPU went to 100% or over. Link to comment Share on other sites More sharing options...
Arakasi 549 Posted November 7, 2014 Share Posted November 7, 2014 Its the only logical explaination. Maybe ESET can check the code behind decompression or at least the API being used in the background, if updates come compressed for smaller size. Link to comment Share on other sites More sharing options...
ESET Insiders m4v3r1ck 118 Posted November 12, 2014 ESET Insiders Share Posted November 12, 2014 Hi all, Having the same 100% cpu usage when ECSP (5.0.115.0) is updating the Virus Signature Database: Link to comment Share on other sites More sharing options...
Most Valued Members planet 232 Posted October 3, 2015 Most Valued Members Share Posted October 3, 2015 (edited) Happy to say that version 6.1.12.0 of ECS and ECSP improved the way updates are done and also resolved this CPU issue whilst updating. (Now only about 10% CPU for the first large VSD update). Edited October 3, 2015 by planet Link to comment Share on other sites More sharing options...
Recommended Posts