Hello,
I'm trying to debug a .net windows service that is spending lot of his time in GC.
Using windbg during collections I discovered that most of the time is spent in:
00000000`0279e8e0 00000642`7f5368a3 mscorwks!WKS::gc_heap::plan_phase+0x50c
00000000`0279ea90 00000642`7f94ef4e mscorwks!WKS::gc_heap::gc1+0x73
00000000`0279eae0 00000642`7f51c259 mscorwks!WKS::gc_heap::garbage_collect+0x29e
00000000`0279eb40 00000642`7f4eb56e mscorwks!WKS::GCHeap::GarbageCollectGeneration+0x199
00000000`0279ebd0 00000642`7f4ea49d mscorwks!WKS::gc_heap::try_allocate_more_space+0x38e
00000000`0279eca0 00000642`7f4e9cef mscorwks!WKS::GCHeap::Alloc+0x6d
00000000`0279ecd0 00000642`7f9b35da mscorwks!FastAllocateObject+0xaf
The pattern of Gen0,Gen1,Gen2 collections is reasonable (100,10,1)
Please note that the application runs on x64 and has a really large heap:
Gen0 10M
Gen1 26K
Gen2 4,371M
Large 3,500M
Note: I know about the great Tess Ferrandez blog.