<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jul 8, 2014 at 9:08 AM, Max Leske <span dir="ltr"><<a href="mailto:maxleske@gmail.com" target="_blank">maxleske@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><div style="word-wrap:break-word"><div>Hi folks</div><div><br></div><div>As promised a long time ago my colleague Nik Lutz has finalized the patch for the VM that enables socket activation with Systemd. I will quickly go over what the patch is supposed to achieve, how we plan to use socket activation and what (minimal) changes are necessary.</div>
<div><br></div><br><div>Systemd Socket Activation:<br>Systemd opens a (network-) socket and waits for connections. When the first client connects the assotiated service (VM) is started. Systemd indicates via environment variable (LISTEN_FDS) that it opened a network socket.<br>
<font color="#0f61c8"><br></font>Detailed documentation on socket activation with Systemd can be found here: <a href="http://0pointer.de/blog/projects/socket-activation.html" target="_blank">http://0pointer.de/blog/projects/socket-activation.html</a></div>
<div><br></div><div><br></div><div>Our scenario for socket activation: </div><div>At Cmsbox we have hundereds of images running on a server, all of which listen on a dedicated network port for incoming connections. The server is powerful enough to run all these processes concurrently, especially since not every image receives requests all the time.</div>
<div>With socket activation we could further lower the server load and free up resources for images with a high request rate. Images that don’t receive any requests for a specified amount of time can be suspended automatically and reactivated when a request comes in.<br>
</div></div></blockquote><div><br></div><div><br></div><div>OMG, I want that!</div></div></div></div>