11–20 of 39 posts
So 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
Can someone shine some light on why and how this is useful? What are some examples?
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?
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.
Earlier quoted context omitted.
This is an OS-less web server VM, basically an modified Erlang VM to run directly on "almost" bare-metal
Actually, we didn't modify Ericsson's Erlang VM, we have written our own.
The 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 ).
Earlier quoted context omitted.
Actually, we didn't modify Ericsson's Erlang VM, we have written our own.
Impressive, is that what Zerg is about? where can I find more information about this?
Earlier quoted context omitted.
Impressive, is that what Zerg is about? where can I find more information about this?
http://en.wikipedia.org/wiki/Zergling#Zerg or http://knowyourmeme.com/memes/zerg-rush
one thing I haven't been able to wrap my head around is why "on xen"? couldn't this be done "on qemu" as well, or even 'more betterly'?