Hacker Newsnew | past | comments | ask | show | jobs | submit | scprodigy's commentslogin

Hyper.sh is faster, launching your Docker image in 5 seconds.


What control do you have?


How long does it take launch it on triton?


Did you try the test with a FIP?


A what? :)



Ah, no I did not. I suppose it's possible that nat-ing to an internal ip is more contested than routing/nat-ing to a floating ip.


In my experience, it takes 1min to launch a container in Triton, but 5-10s in Hyper.



No, they are in different games basically.


Let's say you have two images: web and db. Web containers ask for high cpu, but small disk. DB requires big mem and disk.

With GKE, you either have different instance types for different container sizes; or you launch the BIG&TALL VMs for all.

The same story applies to public/private network as well. Point is that in GKE, there are two layers to manage: VM and Containers. In Hyper, the container is the infra.


That's a terrible argument considering Hyper gives you no fine-grained control over instance types. You just get a linearly-increasing allocation of CPU cores and RAM.


Don't think so. Though their stack are open source.


They don't use Linux container, they use hypervisor-based container (see: github.com/hyperhq/hyperd). Therefore it is VM-level isolation.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: