[Python-Dev] Investigating Python memory footprint of one real Web application
Victor Stinner
victor.stinner at gmail.com
Tue Jan 24 09:08:03 EST 2017
More information about the Python-Dev mailing list
Tue Jan 24 09:08:03 EST 2017
- Previous message (by thread): [Python-Dev] Investigating Python memory footprint of one real Web application
- Next message (by thread): [Python-Dev] Investigating Python memory footprint of one real Web application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2017-01-24 15:00 GMT+01:00 INADA Naoki <songofacandy at gmail.com>: > And here are top 3 tracebacks from tracemalloc: > > 15109615 (/180598) > File "<frozen importlib._bootstrap_external>", line 488 > File "<frozen importlib._bootstrap_external>", line 780 > File "<frozen importlib._bootstrap_external>", line 675 > File "<frozen importlib._bootstrap>", line 655 FYI at Python startup, usually the largest memory block comes from the dictionary used to intern all strings ("interned" in unicodeobject.c). The traceback is never revelant for this specific object. Victor
- Previous message (by thread): [Python-Dev] Investigating Python memory footprint of one real Web application
- Next message (by thread): [Python-Dev] Investigating Python memory footprint of one real Web application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list