From 3ca42741cbc14373b0523be310c8e6d52efdb5ef Mon Sep 17 00:00:00 2001 From: Justin Ethier Date: Wed, 20 Jan 2016 23:02:00 -0500 Subject: [PATCH] Update Garbage-Collector.md --- docs/Garbage-Collector.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Garbage-Collector.md b/docs/Garbage-Collector.md index 62ceb66f..50ca87bf 100644 --- a/docs/Garbage-Collector.md +++ b/docs/Garbage-Collector.md @@ -241,7 +241,7 @@ Limitations or potential issues: - Heap memory fragmentation has not been addressed and could be an issue for long-running programs. Traditionally a compaction process is used to defragment a heap. An alternative strategy has also been suggested by Pizlo: -> instead of copying objects to evacuate fragmented regions of the heap, fragmentation is instead embraced. A fragmented heap is allowed to stay fragmented, but the collector ensures that it can still satisfy allocation requests even if no large enough contiguous free region of space exists. + > instead of copying objects to evacuate fragmented regions of the heap, fragmentation is instead embraced. A fragmented heap is allowed to stay fragmented, but the collector ensures that it can still satisfy allocation requests even if no large enough contiguous free region of space exists. - Accordingly, the runtime needs to be able to handle large objects that could potentially span one or more pages. - There is probably too much heap locking going on, and this could be an issue for a large heap and/or a large number of mutators. Improvements can likely be made in this area.