Kaseya Community

Kserver process W3WP too much RAM

  • We are fresh off moving 150 or so endpoints to our new server and after cleaning up what mess we caused before the weekend, the server has settled down with 1 exception. After we restart IIS, the process W3WP loads maybe 70MB ram. As we access kaseya pages, this seems to grow with every different page viewed. We have edited the aspnet.config file to set gc to false (garbage collection) per advice on a search, seems to help some but its still gtowing. What size should this file be and what do all you experience?
    Its real fast growing to 280MB with 1 user???
    TIA
    Bob Aubry on Pats login
    Main Street Software, Inc.
    email boba@mssinc.com
    voice 717-898-2946

    Legacy Forum Name: Kserver process W3WP too much RAM,
    Legacy Posted By Username: Mssinc
  • We did some research on W3WP not releasing RAM. This AM with just 2 users in VSA, that process was up to 418MB around 10:30AM. We found that there is a garbagecollection process that is supposed to run to free up RAM, but with multiple CPU's it consumes too much. So we have edited aspnet.config and added:

    But what seems to have fixed the problem was in IIS Manager/App Pools/Kaseya/Properties we checked the box to limit RAM to 192MB. The W3WP process immediatley went down to 78MB and is now peaking at 148MB.
    What are the best practices with this?
    Thanks!
    Bob Aubry from Pat's login
    Main Street Software

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: Mssinc
  • Mssinc
    We did some research on W3WP not releasing RAM. This AM with just 2 users in VSA, that process was up to 418MB around 10:30AM. We found that there is a garbagecollection process that is supposed to run to free up RAM, but with multiple CPU's it consumes too much. So we have edited aspnet.config and added:

    But what seems to have fixed the problem was in IIS Manager/App Pools/Kaseya/Properties we checked the box to limit RAM to 192MB. The W3WP process immediatley went down to 78MB and is now peaking at 148MB.
    What are the best practices with this?
    Thanks!
    Bob Aubry from Pat's login
    Main Street Software



    Wow! , we had the same issue, agents falling offline, Kserver not available and we tried this fix. OMG! Live Connect comes up so fast now i had to come back here and say THANK YOU!!

    FYI: We're running a VM kserver with 4G of RAM and 4 virtual CPU's on a IBM 37XX ESX 3.5 Server


    Wink

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: RichardMiller