暫停C#的GC

源： http://stackoverflow.com/questions/6005865/prevent-net-garbage-collection-for-short-period-of-time

 

GCLatencyMode oldMode = GCSettings.LatencyMode;// Make sure we can always go to the catch block, // so we can set the latency mode back to `oldMode`RuntimeHelpers.PrepareConstrainedRegions();try{    GCSettings.LatencyMode = GCLatencyMode.LowLatency;    // Generation 2 garbage collection is now    // deferred, except in extremely low-memory situations}finally{    // ALWAYS set the latency mode back    GCSettings.LatencyMode = oldMode;}

That will allow you to disable the GC as much as you can. It won't do any large collections of objects until:

• You call GC.Collect()
• You set GCSettings.LatencyMode to something other than LowLatency
• The OS sends a low-memory signal to the CLR

Please be careful when doing this, because memory usage can climb extremely fast while you're in thattry block. If the GC is collecting, it's doing it for a reason, and you should only seriously consider this if you have a large amount of memory on your system.

In reference to question three, perhaps you can try reusing objects like byte arrays if you're receiving information through filesystem I/O or a network? If you're parsing that information into custom classes, try reusing those too, but I can't give too much good advice without knowing more about what exactly you're doing.

Here are some MSDN articles that can help too:

• Latency Modes
• Constrained Execution Regions (this is why we call PrepareConstrainedRegions())