I'm seeing 1.5 to 1.6 secs. Is that due to my crappy internet connection or is that simply what it is? Because 1.5 secs per request, and more for somewhat more complex operations, seems long to me. As instance startup time it is impressive though! But they are designed to die after each request, right? Or is that just this example?
Zerg demo – Xen instance spawned for each web request
31–39 of 39 posts
Re: Zerg demo – Xen instance spawned for each web request
#32Re: Zerg demo – Xen instance spawned for each web request
#33I tweaked the background image URLs so they'd be absolute instead of relative, but otherwise it's unmodified.
Re: Zerg demo – Xen instance spawned for each web request
#34If you run Perl in CGI it creates a new VM for every single request. How is this different?
Re: Zerg demo – Xen instance spawned for each web request
#35Re: Zerg demo – Xen instance spawned for each web request
#36For people who are interested but unable to get a connection, here's a saved page: http://f.cl.ly/items/07293W450C3F0r472u1O/Zerg%20demo%20-%20... I tweaked the background image URLs so they'd be absolute instead of relative, but otherwise it's unmodified.
Re: Zerg demo – Xen instance spawned for each web request
#37Can someone shine some light on why and how this is useful? What are some examples?
The folks at ZeroVM have a list of motivations[1] for this type of execution and hosting model. The only problem is that it's hard to tell how active the project is from their main page alone. EDIT: Their github commit is fairly active for a solo developer[2]. [1] http://zerovm.org/motivation/ [2] https://github.com/zerovm/zerovm/commits/master
Re: Zerg demo – Xen instance spawned for each web request
#38If you run Perl in CGI it creates a new VM for every single request. How is this different?
These are very different things.