| ▲ | ahepp 16 hours ago |
| What drove you to choose that over something like containers? |
|
| ▲ | droelf 14 hours ago | parent | next [-] |
| Yeah, boot time, isolation (proper VM vs containers), and ease of use on a larger Hetzner box. |
| |
| ▲ | ahepp 13 hours ago | parent [-] | | Did you notice a substantial difference in those factors between more traditional micro VMs that use OCI images (like Firecracker) and unikernels? |
|
|
| ▲ | m00dy 16 hours ago | parent | prev [-] |
| shorter cold-boot times. |
| |
| ▲ | ahepp 14 hours ago | parent | next [-] | | If we’re talking about cold boot times, wouldn’t the relevant metric for unikernels be the hypervisor’s boot time? | |
| ▲ | zozbot234 13 hours ago | parent | prev [-] | | How would that compare with containers running on Firecracker or other virtio-based μVM's? | | |
| ▲ | wmf 13 hours ago | parent [-] | | A unikernel on Firecracker is probably going to start faster than a container on Linux on Firecracker. | | |
| ▲ | ahepp 13 hours ago | parent [-] | | I assume they meant using an OCI image for the rootfs of a firecracker VM, not running a container inside a firecracker VM. Still difficult to see how the unikernel could be slower, but I doubt the difference would be huge? Don't have anything to back that up though. |
|
|
|