Zerg demo – Xen instance spawned for each web request
zerg.erlangonxen.org
Zerg demo – Xen instance spawned for each web request
1–10 of 39 posts
Re: Zerg demo – Xen instance spawned for each web request
#2I'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?
Re: Zerg demo – Xen instance spawned for each web request
#3I'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?
Right, it's just example, right, it dies after each request - you can check the code on github. Also, you can review the detailed structure of time spending on the second half of zerg's page.
Re: Zerg demo – Xen instance spawned for each web request
#4Can someone shine some light on why and how this is useful? What are some examples?
Re: Zerg demo – Xen instance spawned for each web request
#5It keeps saying "Over capacity", I want to know what this is about though.
Re: Zerg demo – Xen instance spawned for each web request
#6So what's being shown off here? Clearly it's impressive that a web server VM is loaded so quickly, but what's the key? Is it a carefully configured Xen VM? Or is it the use of Erlang?
Re: Zerg demo – Xen instance spawned for each web request
#7It keeps saying "Over capacity", I want to know what this is about though.
About being able to quickly scale to capacity. :)
Re: Zerg demo – Xen instance spawned for each web request
#8I'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?
It is just an example to show how quickly they can provision a new vm+server. They are not advocating for it to be a good way to serve requests.
Re: Zerg demo – Xen instance spawned for each web request
#9The demo about the vm+server startup time is interesting, but I am glad to know about the way they use Nginx to proxy the request twice to do the provisioning of the vm+server.
Edit: I wonder if the numbers would be similar if the example was done with HaLVM (https://github.com/GaloisInc/HaLVM).
Re: Zerg demo – Xen instance spawned for each web request
#10So what's being shown off here? Clearly it's impressive that a web server VM is loaded so quickly, but what's the key? Is it a carefully configured Xen VM? Or is it the use of Erlang?
This is an OS-less web server VM, basically an modified Erlang VM to run directly on "almost" bare-metal