Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #78662

Re: "High water" Memory fragmentation still a thing?

From Antoine Pitrou <antoine@python.org>
Subject Re: "High water" Memory fragmentation still a thing?
Date 2014-10-03 19:16 +0000
References <CANm61jc=pB7n+5kuea6bmYXTbo3hXLT8d4JZx3Yq-TBtgGrFOQ@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.14582.1412363831.18130.python-list@python.org> (permalink)

Show all headers | View raw


Hello,

Croepha <croepha <at> gmail.com> writes:
> 
> Question:
> 
> Does python in general terms (apart from extensions or gc manipulation),
exhibit a "high water" type leak of allocated memory in recent python
versions (2.7+)?

It is not a leak. It is a quite common pattern of memory fragmentation.
The article is wrong in assuming that Python doesn't return the memory to
the OS. Python does return its empty memory pools to the OS, however the OS
itself may not be able to release that memory, because of heap fragmentation.

As the article mentions, this was improved (mostly fixed?) in 3.3.

Regards

Antoine.

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread


Thread

Re: "High water" Memory fragmentation still a thing? Antoine Pitrou <antoine@python.org> - 2014-10-03 19:16 +0000

csiph-web