This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos 9.01 Memory Usage out of Control

Memory Usage seems to be way up with version 9.  I mean really this is insane

SophosScanD 268MB

SophosANtiVirus 157MB

InterCheck 220MB

Sophos UI 12MB

Sophos SXLD 7MB

SophosConfigD 4MB

Sophos Autoupdate 11MB

I add these up and  get 679MB. I just removed it and loaded 8.x latest and get less than 200MB.  That is more than 3 times the amount of memory.  I tried this on a Mac Mini 2012 and a MacBook Pro late 2011 all with 10.8.4

:1013192


This thread was automatically locked due to age.
Parents
  • Hi mikedvzo,

    Not able to give you any insight for other vendors (security products or otherwise) but for our product the significant memory consumption is actually detection data. To speed scanning all the detection data is in memory. The more types of threats we detect, the more detection data is needed. The more complicated detections require more memory, because it takes more complex code to differentiate malicious software vs. clean software. Its a never ending situation. The team in SophosLabs (who maintain the detection data) do take memory consumption seriously, but its a hard problem.

    Today we have several scanning processes, each using a copy of the detection. The "easy win" in the future will be to reduce the number of copies of the detection data needed. I say "easy" because its easy to say that. Its more effort to actually rework the product architecture, but we know what to do and its on the roadmap for this year.

    :1013393

    ---

    Bob Cook (bob.cook@sophos.com) Director, Software Development

Reply
  • Hi mikedvzo,

    Not able to give you any insight for other vendors (security products or otherwise) but for our product the significant memory consumption is actually detection data. To speed scanning all the detection data is in memory. The more types of threats we detect, the more detection data is needed. The more complicated detections require more memory, because it takes more complex code to differentiate malicious software vs. clean software. Its a never ending situation. The team in SophosLabs (who maintain the detection data) do take memory consumption seriously, but its a hard problem.

    Today we have several scanning processes, each using a copy of the detection. The "easy win" in the future will be to reduce the number of copies of the detection data needed. I say "easy" because its easy to say that. Its more effort to actually rework the product architecture, but we know what to do and its on the roadmap for this year.

    :1013393

    ---

    Bob Cook (bob.cook@sophos.com) Director, Software Development

Children
No Data