3.14 Analysis: Garbage Collection

The suggested length is 5 pages.

Write a paper about garbage collection.

You can write about whatever you want provided you demonstrate a solid understanding. Here are a few suggestions you might consider in starting this assignment, but please do not feel constrained by this list, as it is not comprehensive. Please feel free to contact me directly so we can discuss the direction you want to take with the paper.

- Discuss what is good, bad, ugly, and awesome about reference counting.

- Discuss what is good, bad, ugly, and awesome about mark & sweep.

- Discuss what is good, bad, ugly, and awesome about stop & copy.

- Discuss the special considerations that large objects require of a garbage collector.

- Discuss the implications of garbage collected and non-garbage collected code interacting, such as Java and C.

- Discuss object header contents and placement options.

- Discuss what makes generational collectors difficult to implement.

- Discuss the intergenerational hypothesis. Do you believe it is true for programs that you write? Can you think of kinds of programs where it definitely is or is not true?

- Learn about region-based memory management and discuss it.

- Discuss the trade-offs of using or not using garbage collection. Are there certain domains where you feel it is necessary? Are there any domains you feel are particularly bad to garbage collect?

- Discuss how garbage collection relates to modularity.

Refer to Language Analysis the First for details about including citations, history, code, etc in your writing in this class.