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


Groups > comp.lang.python > #78708

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-05 00:10 +0000
References <CANm61jc=pB7n+5kuea6bmYXTbo3hXLT8d4JZx3Yq-TBtgGrFOQ@mail.gmail.com> <loom.20141003T211459-72@post.gmane.org> <m0mun6$8hr$1@ger.gmane.org>
Newsgroups comp.lang.python
Message-ID <mailman.14608.1412467850.18130.python-list@python.org> (permalink)

Show all headers | View raw


Christian Heimes <christian <at> python.org> writes:
> 
> The article doesn't state if the writer is referring to virtual memory
> or resident set size.

Actually the article mentions the following recipe:

  resource.getrusage(resource.RUSAGE_SELF).ru_maxrss

which means the author is probably looking at resident set size.

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-05 00:10 +0000

csiph-web