We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GetCurrentProcessMemoryUsage method creates a new Process object on every method call:
public ulong GetCurrentProcessMemoryUsage() { using Process process = Process.GetCurrentProcess(); return (ulong)process.WorkingSet64; }
Instead, it could have created it once and then reusing it for the application lifetime. This should improve performance.
The text was updated successfully, but these errors were encountered:
This might hit performance issue:
Sorry, something went wrong.
Not sure why GetCurrentProcess is really cpu-heavy
Fixed in #5597
evgenyfedorov2
No branches or pull requests
GetCurrentProcessMemoryUsage method creates a new Process object on every method call:
Instead, it could have created it once and then reusing it for the application lifetime. This should improve performance.
The text was updated successfully, but these errors were encountered: