For AWS Lambda, which is better "Workstation GC" or "Server GC".

[sudoudaisuke]

Hi there.
I have read some blog that "Workstation GC" is better than "Server GC" for AWS lambda. But I can't find AWS document for dotnet GC. Could you tell me which one is better?

https://levelup.gitconnected.com/improving-memory-usage-and-stability-on-aws-lambda-net-7c0c47c5b52e
https://dev.to/aws-builders/optimize-memory-usage-in-aws-lambda-net-with-a-simple-fix-412h

My project settings

• dotnet 6
• Http API (ApiGateway)
• Use Provisioning Concurrency
• Use DynamoDB

[ashishdhingra]

@sudoudaisuke Most of the time you need not manage garbage collection by yourself if you are disposing off the resources properly in your application logic. Based on the 1st article, it proposes the following:

There are 2 types of garbage collection in dotnet core: Workstation GC and Server GC. Server GC is optimized for server usage, under the assumption that CPU usage is more highly prioritized than memory. This type of garbage collection allows for much higher memory usage, which might be no problem on a big server, but for Lambda functions where memory is very often scarce (we are paying for it after all!) this might not always be the best approach. Workstation GC can in many cases be more performant when memory is limited, such as for serverless functions or docker containers with limited resources available.

So, it appears that Workstation GC might be the better approach for Lambda environment where memory is limited.