My pleasure! I look forward to the review of the book 😉

Thank you for your valuable comment Konrad 🙂
I modified the article a bit in these misleading places according to your remarks.
Looking forward to your book assuming you dig into these details that deeply 😉

Cheers!
Dawid

“after the full GC cycle generation 0 and generation 1 become empty”

Nope. During full GC objects from gen0 are promoted to gen1 so it does not have to be empty.

“normally using static data should be avoided as much as possible and reasonable”

Long living objects in gen2 (like statics) are not a problem by itself. Just by the fact that they are there does not mean full GCs will be triggered. The main problem are objects that are living just long enough to be promoted to gen2 (possibly triggering full GC) and die there soon (putting the work on the GC)

“card table stores this information per “bit”, which represents 128 bytes of managed memory”

128 bytes in 32-bit, 256 bytes in 64-bit. And due to write barrier optimization, no single bit is manipulated but the entire byte. So, in fact making such older-to-younger reference marks 2048 bytes as potential roots region.