Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 89 replies
  • Subscribers 4 subscribers
  • Views 84222 views
  • Users 0 members are here
Options
Suggested
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

Memory swap usage 9.1GA and UTM220

Simon Shaw
We have a UTM220 device, upgraded to 9.1 yesterday.

40 devices/users protected.
Network Visibility, POP3 Proxy, RED, Endpoint Protection, WAF and HA are all OFF.
HTTP Proxy web caching is off.
IPS is using only 7980 of 15806 patterns.

75-300 users are recommended by Sophos for this unit type.

However memory swap climbed almost instantly to over 50% of RAM.  I know there has been some discussion on swap usage, but am unsure of the outcome.  CPU looks fine.

Memory.png

Can someone send me a summary of Sophos comments on swap/memory usage as I'd really not like to throw 100-200 users on this device...


This thread was automatically locked due to age.
Parents
  • 0
    Luckman, if this is your own PC and not a Sophos Appliance, first, try as root, cc set ips num_instances 1

    Did that help?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Luckman, if this is your own PC and not a Sophos Appliance, first, try as root, cc set ips num_instances 1

    Did that help?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    Bob
    Thanks for trying to help. It is an ASG220 appliance (in production) - not a VM etc. I have for now disabled both IPS as well as Web Filtering as both of them seem to have issues with 9.1 (even the most recent 9.101-12) with both 'httpproxy' and 'snort_inline' processes spinning wildly out of control pegging the CPU at 100%.

    Now CPU usage is back to 
Unfiltered HTML