Recommended Posts

Win 10 2004 updated to new beta via manual updates. All seems okay so far.

So a2start will still show the 0..1..2..0..1 in task manager CPU details?

It took a little while to start protection after update.

 

Annotation 2020-06-26 160451.jpg
Download Image

Share this post


Link to post
Share on other sites
24 minutes ago, stapp said:

So a2start will still show the 0..1..2..0..1 in task manager CPU details?

a2start CPU and RAM usage should be improved in beta 2020.7.0.10259, we're still on that.

 

Share this post


Link to post
Share on other sites
4 minutes ago, Frank H said:

a2start CPU and RAM usage should be improved in beta 2020.7.0.10259, we're still on that.

 

I may need to restart machine as my a2start is usually quite low but it hasn't dropped much at all since I updated.

Share this post


Link to post
Share on other sites

I've waited a few days to see how 10259 seems to be behaving and it's certainly looking a lot better - cpu has stayed low.

However I just got to teh end of a custom scan - which was long running - just over 4 hours; two drives (both SSDs, though one is fairly empty), 1.4 million files.  The scan looked inside archives which is why it took so long (a scan of the same disks but skipping archives usually takes around 70-75 minutes).  Also debug logging is on.

But, see this summary from Process Hacker.   A2start, during the scan had a WS of 1.1 GB, and still does now that the scan is finished.  It peaked at 1.11 GB and peak virtual memory use was 1.41 GB.   It's a hell of a lot for a process that's supposedly only doing the user-facing stuff.   When I was watching the scan running, near the end, a2service - the bit that as far as I know is actually doing the work - was using around 770 MB.   I don't understand how a2start can be using more memory then the scanner itself.

20200629 a2start end of scan - WS.jpg
Download Image

Share this post


Link to post
Share on other sites
On 6/29/2020 at 12:32 AM, JeremyNicoll said:

But, see this summary from Process Hacker.   A2start, during the scan had a WS of 1.1 GB, and still does now that the scan is finished.  It peaked at 1.11 GB and peak virtual memory use was 1.41 GB.   It's a hell of a lot for a process that's supposedly only doing the user-facing stuff.   When I was watching the scan running, near the end, a2service - the bit that as far as I know is actually doing the work - was using around 770 MB.   I don't understand how a2start can be using more memory then the scanner itself.

Thanks for your feedback.
We are investigating this already.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.