Is there a way to find out how much memory specific variables are using? Google isn't helping

This page summarizes the projects mentioned and recommended in the original post on /r/PowerShell

WorkOS
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors

  • SqlClient

    Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.

    • If you're connecting to SQL Server, connection pooling can be a common cause of apparent memory leaks. If you're opening and closing hundreds of connections, the pool may not be disposing of the connections quickly enough. Or you might be running into issues like this one. You might want to look at SqlConnection.ClearAllPools or SqlConnection.ClearPool or simply disabling connection pooling entirely in the connection string.

  • PowerShell.DebuggingTools

    Discontinued Repository PowerShell.DebuggingTools created on December 16, 2022 5:39 PM by desktop-1lebrea\gp

    • The following PowerShell script uses the API's SetProcessWorkingSetSizeEx.aspx)

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts