Gimme all processes using >= 200MB Working Set Size (64-bit) on...well, any OS that can run PowerShell Core (Linux, Mac, Windows)

ps.ps1

#!/usr/bin/env pwsh

# Uses Get-Process piped to some stuff to get a list of processes
# over a certain amount of memory and output those as JSON.
# Takes no arguments.

# NOTE: This threshold is defined as BYTES, not KILOBYTES like the shell script.
# Adjust the math accordingly.

$threshold = (200 * 1024) * 1024 # Don't report anything greater than 200MB
$procs = Get-Process | Where-Object { $_.WorkingSet64 -gt $threshold }
$procs | Select-Object -Property CommandLine,WorkingSet64,Id | ConvertTo-Json

# We can do this with PowerShell without tainting output redirection to file;
# not so with bash|zsh! Set $VerbosePreference = 'Continue' to see this.
Write-Verbose "Found $($procs.Count) processes exceeding threshold"
Write-Verbose "Threshold: $($threshold / 1024 / 1024)MB"

# Compare how smooth and easy this is with the shell script equivalent:
# https://gist.github.com/jahio/5eaacad1c23a00f96137fd13cf3a7b16
#
# I know which one I'd rather work with!

I found your gists from here : I switched from bash to powershell and its going great. I made the assumption that the author of the article was the author of the gists as well. Didn't think to check both and compare 😄

Ah, yes, I did indeed write that article. When Qarik bought out Stark and Wayne and later made significant organizational changes, they changed all the authors names on existing articles. That's also why I asked - if it was this as I suspected, I literally can't get in there to change anything anymore. Good suggestion, though!

(Edited slightly because lawyers)