Facundo Batista facundobatista at gmail.com
Mon Jul 17 10:56:56 EDT 2017

• Previous message (by thread): [Python-Dev] Impact of Namedtuple on startup time
• Next message (by thread): [Python-Dev] Impact of Namedtuple on startup time
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Mon, Jul 17, 2017 at 9:43 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:

> As for 2), startup time is actually a very important consideration
> nowadays, both for small scripts *and* for interactive use with the
> now very wide-spread use of Jupyter Notebooks.  A 1 ms. cost when
> importing a single module can translate into a large slowdown when your
> library imports (directly or indirectly) hundreds of modules, many of
> which may create their own namedtuple classes.

My experience inside Canonical is that golang stole a lot of "codebase
share" from Python, and (others and mine) talks hit two walls, mainly:
one is memory consumption, and the other is startup time.

So yes, startup time is important for user-faced scripts and services.

Regards,

-- 
.    Facundo

Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
Twitter: @facundobatista

---

• Previous message (by thread): [Python-Dev] Impact of Namedtuple on startup time
• Next message (by thread): [Python-Dev] Impact of Namedtuple on startup time
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list