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/2017-January/147194.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
Fri Jan 20 05:49:01 EST 2017
Hi, all.

After reading Instagram's blog article [1], I’m thinking about how
Python can reduce memory usage of Web applications.
My company creating API server with Flask, SQLAlchemy and typing.
(sorry, it's closed source).
So I can get some data from it's codebase.

[1]: https://engineering.instagram.com/dismissing-python-garbage-collection-at-instagram-4dca40b29172#.lenebvdgn

Report is here
https://gist.github.com/methane/ce723adb9a4d32d32dc7525b738d3c31


My thoughts are:

* Interning (None,) seems worth enough.

* There are many empty dicts.  Allocating ma_keys lazily may reduce
memory usage.

* Most large strings are docstring.  Is it worth enough that option
for trim docstrings, without disabling asserts?

* typing may increase memory footprint, through functions
__attributes__ and abc.
   * Can we add option to remove or lazy evaluate __attributes__ ?
   * Using string literal for annotating generic type may reduce WeakRef usage.
   * Since typing will be used very widely in this year.  Need more
investigating.
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