A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2017-January/147248.html below:

[Python-Dev] Investigating Python memory footprint of one real Web application

[Python-Dev] Investigating Python memory footprint of one real Web application [Python-Dev] Investigating Python memory footprint of one real Web applicationINADA Naoki songofacandy at gmail.com
Wed Jan 25 13:35:15 EST 2017
On Thu, Jan 26, 2017 at 2:33 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Wed, 25 Jan 2017 20:54:02 +0900
> INADA Naoki <songofacandy at gmail.com> wrote:
>>
>> ## Stripped annotation + without pydebug
>
> Does this mean the other measurements were done with pydebug enabled?
> pydebug is not meant to be used on production systems so, without
> wanting to disparage the effort this went into these measurements, I'm
> afraid that makes them not very useful.
>
> Regards
>
> Antoine.

Yes.  I used sys.getobjects() API which is available only in pydebug mode.
Since it adds two words to all objects for doubly linked list,  I did
sys.getsizeof(o) - 16
when calculating memory used by each type.

While it may bit different from --without-pydebug, I believe it's
useful enough to
estimate how much memory is used by each types.
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