Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #78708 > unrolled thread
| Started by | Antoine Pitrou <antoine@python.org> |
|---|---|
| First post | 2014-10-05 00:10 +0000 |
| Last post | 2014-10-05 00:10 +0000 |
| Articles | 1 — 1 participant |
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.
Re: "High water" Memory fragmentation still a thing? Antoine Pitrou <antoine@python.org> - 2014-10-05 00:10 +0000
| From | Antoine Pitrou <antoine@python.org> |
|---|---|
| Date | 2014-10-05 00:10 +0000 |
| Subject | Re: "High water" Memory fragmentation still a thing? |
| Message-ID | <mailman.14608.1412467850.18130.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web