[Python-Dev] startup time repeated? why not daemon (original) (raw)

Gregory P. Smith greg at krypto.org
Thu Jul 20 20:49:31 EDT 2017


On Thu, Jul 20, 2017 at 10:56 AM Jim J. Jewett <jimjjewett at gmail.com> wrote:

I agree that startup time is a problem, but I wonder if some of the pain could be mitigated by using a persistent process.

This is one strategy that works under some situations, but not all.

There are downsides to daemons:

For example, in

https://mail.python.org/pipermail/python-dev/2017-July/148664.html Ben Hoyt mentions that the Google Cloud SDK (CLI) team has found it "especially problematic for shell tab completion helpers, because every time you press tab the shell has to load your Python program"

I can imagine a daemon working well in this specific example.

Is it too hard to create a daemon server?

That is my take on it.

Is the communication and context switch slower than a new startup?

Is the pattern just not well-enough advertised?

I have experienced good daemon processes. Bazel (a Java based build system) uses that approach.

I can imagine Mercurial being able to do so as well but have no idea if they've looked into it or not.

Daemons are by their nature an application specific thing.

-gps -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170721/dbbe0179/attachment.html>



More information about the Python-Dev mailing list