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

Groups > comp.lang.python > #78663 > unrolled thread

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

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: "High water" Memory fragmentation still a thing? Christian Heimes <christian@python.org> - 2014-10-03 21:51 +0200

#78663 — Re: "High water" Memory fragmentation still a thing?

On 03.10.2014 21:16, Antoine Pitrou wrote:
> 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.

The article doesn't state if the writer is referring to virtual memory
or resident set size. For long-running 32bit processes it is quite
common to run out of virtual address space. But that's something totally
different than running out of memory. A 64bit process can have a virtual
address size of several GB but only occupy a few hundred MB of physical
memory. People tend to confuse the meaning of VSZ and RSS and forget
about paging.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web