How to monitor RAM and CPU on Windows VPS without paid tools

Connect via RDP and open Task Manager with Ctrl+Shift+Esc. If the compact version appears, click “More details” in the bottom-left corner to expand it.

Switch to the “Performance” tab — you will see real-time graphs for CPU, Memory, Disk and Ethernet. Click “Memory” to see RAM details.

Identify the numbers that matter on the memory pane:

• In use: physical RAM currently held by processes.
• Available: free RAM + standby (cache that can be reclaimed).
• Committed: total reserved including pagefile, in the “current/max” format.
• Cached: standby data that can be discarded if another process needs it.

If “Committed” is close to the max, the system is leaning hard on the pagefile. Add RAM or identify the process leaking memory.

Switch to the “Details” tab and click the “Memory (private working set)” column header to sort from largest to smallest. The top 5 processes account for 80% of consumption on most servers.

For CPU, sort by the “CPU” column — but be aware: the displayed value is instantaneous and fluctuates heavily. For a reliable average, use Resource Monitor.

Press Win+R, type resmon and hit Enter. The window has 5 tabs: Overview, CPU, Memory, Disk, Network. The graphs on the right refresh every second.

Switch to the “Memory” tab. You will see processes sorted by usage, with Commit, Working Set, Shareable and Private columns. The difference compared to Task Manager is the bottom graph — “Used Physical Memory” shows hardware as a horizontal bar: Hardware Reserved, In Use, Modified, Standby and Free.

To investigate CPU, switch to the “CPU” tab. Tick the checkbox of a process in the list — the “Associated Modules” panel shows which DLLs it is executing, and “Associated Handles” lists files and registry keys it has open.

This cross-reference reveals things Task Manager does not: for example, a w3wp.exe (IIS) burning CPU because it is blocked on a log file another process left locked.

Open Performance Monitor (perfmon.exe). In the left pane, expand “Data Collector Sets” → “User Defined”. Right-click → New → Data Collector Set.

Name: RAM_CPU_Baseline. Select “Create manually (Advanced)” and click Next. Tick “Performance counter” and Next.

Under “Performance counters”, click Add and select these essential counters:

\Processor(_Total)\% Processor Time
\Memory\Available MBytes
\Memory\Committed Bytes
\Memory\Pages/sec
\Memory\Page Faults/sec
\Process(*)\Working Set
\Process(*)\% Processor Time
\System\Processor Queue Length

Set “Sample interval” to 15 seconds. In production, 60 seconds is enough — intervals that are too short generate huge files without gaining precision.

Pick the output directory (default %systemdrive%\PerfLogs\Admin\RAM_CPU_Baseline). Click Finish. Right-click the new Data Collector Set → Start. Collection begins immediately in the binary .blg format.

To stop after a few hours, right-click → Stop. The file appears under “Reports” → “User Defined” → your set. Double-click to open the historical graph.

For a quick snapshot of RAM and CPU right now, run in PowerShell:

Get-CimInstance Win32_OperatingSystem | Select-Object `
  @{N='RAM_Total_GB';E={[math]::Round($_.TotalVisibleMemorySize/1MB,2)}}, `
  @{N='RAM_Free_GB';E={[math]::Round($_.FreePhysicalMemory/1MB,2)}}, `
  @{N='RAM_Used_Pct';E={[math]::Round((($_.TotalVisibleMemorySize - $_.FreePhysicalMemory) / $_.TotalVisibleMemorySize) * 100, 2)}}

Get-CimInstance Win32_Processor | Select-Object Name, LoadPercentage

The result shows total RAM, free RAM and usage percentage, plus the average CPU load at the moment.

To identify the top 10 RAM-consuming processes, sorted:

Get-Process | Sort-Object WorkingSet64 -Descending |
  Select-Object -First 10 `
    Name, Id, `
    @{N='RAM_MB';E={[math]::Round($_.WorkingSet64/1MB,2)}}, `
    @{N='CPU_sec';E={[math]::Round($_.CPU,2)}} |
  Format-Table -AutoSize

The CPU field shows total CPU seconds consumed by the process since it started — useful to spot long-running processes that have accumulated load.

For continuous monitoring every 30 seconds, save this script as monitor.ps1:

while ($true) {
  $ts = Get-Date -Format 'yyyy-MM-dd HH:mm:ss'
  $cpu = (Get-CimInstance Win32_Processor).LoadPercentage
  $os = Get-CimInstance Win32_OperatingSystem
  $ramPct = [math]::Round((($os.TotalVisibleMemorySize - $os.FreePhysicalMemory) / $os.TotalVisibleMemorySize) * 100, 2)
  "$ts CPU=$cpu% RAM=$ramPct%" | Out-File -Append C:\PerfLogs\monitor.log
  Start-Sleep -Seconds 30
}

Run it in the background: Start-Process powershell -ArgumentList "-File C:\scripts\monitor.ps1" -WindowStyle Hidden. The log stays in a simple format, easy to parse with Get-Content later.