A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2015-October/141921.html below:

[Python-Dev] under what circumstances can python still exhibit "high water mark" memory usage?

[Python-Dev] under what circumstances can python still exhibit "high water mark" memory usage? [Python-Dev] under what circumstances can python still exhibit "high water mark" memory usage?Chris Withers chris at simplistix.co.uk
Wed Oct 14 11:26:11 EDT 2015
On 14/10/2015 16:13, Victor Stinner wrote:
> Hi,
>
> You may also try tracemalloc to get stats of the Python memory usage ;-)
>
> The Python memory allocator was optimized in Python 3.3: it now uses
> mmap() when available (on UNIX), it helps to reduce the fragmentation
> of the heap memory. Since Python 3.4, VirtualAlloc() is used for the
> same purpose on Windows.
>
> Please mention your OS, OS version and Python version.
Python 2.7.5 on RHEL 7.1.

Would tracemalloc still be useful here?

cheers,

Chris

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4