This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

High Page/Sec and locking up server and application

Hi,

We have a critical business application (VM) where the Pages/sec starts to increase in the morning then reaches 100% after a few hours then locks the application. In Orion we want to be able to monitor the process that are causing this high Pages/sec and create a trend charts so we can monitor the various process that are causing this high Pages/Sec over time. We have increased memory in the server from 12MB, 16MB, 32MB and it just increases the time it takes to fill up the Pages/Sec to 100% - 2hr, 3hr, 4 hr them 100% then lock the application. In Orion is there a way to monitor the the process that are causing this high Pages/sec.

Thank you,

Scott DeJong

attachments.zip
  • Hi sdejong123‌,

    Do you know what the processes in question are? If so, you can use the Real-time process explorer to setup a new application template to track the individual services/processes and keep an eye on their usages. If your account in SolarWinds has the rights, of course.

  • It looks like you may have a memory leak or a runaway process running on that server. It may be normal, like backups or antivirus, but paging occurs when there is insufficient physical memory in the server to satisfy demand. These pages are then written to virtual memory on disk as temporary storage. The more paging that occurs the more frequently items are swapped between virtual memory (slow) and physical memory (fast). I would recommend using the TopXX Process by Physical Memory and Top XX Processes by Virtual Memory alerts to give you insight into what process(s) are contributing the paging.

    High Memory.png

  • Thank you very much for responding to my question, we actually found out from the software developer there is a memory leak in Windows 2008 R2. We are in the process of upgrading the server to Windows 2012 R2

    Thank you,

    -Scott