mirrors/emacs
1
Fork 0
mirror of git://git.sv.gnu.org/emacs.git synced 2025-12-15 18:40:39 -08:00
Code Issues Projects Releases Wiki Activity

"pig in the python" not just for large objects, as noted by nb in <https://info.ravenbrook.com/project/mps/mail/1997/01/06/14-22/0.txt>

Browse source 
Copied from Perforce
 Change: 187069
 ServerID: perforce.ravenbrook.com
This commit is contained in:
Gareth Rees 2014-09-27 17:16:48 +01:00
parent 655e78f3be
commit 1499ab72af
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
mps/manual/source/glossary/p.rst
View file

@ -302,15 +302,15 @@ Memory Management Glossary: P
.. aka:: *pig in the snake*.
In a :term:`generational <generational garbage collection>`
collector, when a large and long-lived :term:`object` is
collector, when long-lived :term:`objects` are
:term:`allocated` in :term:`nursery space`, collection effort
will be wasted as that object survives and is :term:`promoted
<promotion>` from :term:`generation` to generation. This is
especially noticeable in a :term:`copying collector <copying
garbage collection>`, where the large object will be copied
many times. This difficulty is similar to that of a python
which swallows its prey whole and is somewhat immobilized as
it digests it.
will be wasted as those objects survive and are
:term:`promoted <promotion>` from :term:`generation` to
generation. This is especially noticeable in a :term:`copying
collector <copying garbage collection>`, where long-lived
objects will be copied many times. This difficulty is similar
to that of a python which swallows its prey whole and is
somewhat immobilized as it digests it.
Modern collectors permit objects to be allocated directly into
appropriate generations or pools to avoid this problem.