Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have situation when GC has no time to delete free objects. The code loads a large document into memory and processes it in a loop. If I stop in this loop (in debug mode) or add GC.Collect() the memory usage drops to less then 70 MB.
How do I tune GC? Are there any best practices for tuning GC?
The best tuning here is to leave it alone.
But if your process is really blocking the GC all the time (it shouldn’t), it could help to call
GC.Collect()after some memory consuming part finishes.But we need a lot more info here. What type of application, why (do you think) the GC has no time to do it normally?