Live data from Hacker News

Viewing profile — fhuici

fhuici

HN member
Joined
Mon, Oct 23, 2023, 2:10 PM UTC
HN karma
72
Public activity
49 items

About fhuici

LinkedIn: https://www.linkedin.com/in/felipe-huici-47a559127/ Twitter: @felipehuici E-mail: felipe@unikraft.io

Recent public activity

  1. comment
    Comment #48718612

    FYI, a microVM isn't a small VM, nor necessarily one that has been allocated little RAM. The term comes from the fact that a microVM is launched with Firecracker (a Virtual Machine…

  2. comment
    Comment #40646752

    Current serverless offerings come with a substantial litany of complex, frustrating and expensive issues that together constitute a far cry from the promise of serverless. In this …

  3. story
  4. comment
    Comment #40466614

    On kraft.cloud we use Dockeffiles to build into extremely specialized VMs for deployment. With this in place, we can have say an nginx server cold started and ready to serve at a p…

  5. comment
    Comment #40466560

    We don't need all of those layers and abstractions of course. But if we do things right we also don't need to go the bare metal server route -- cloud platforms, if done right, can …

  6. comment
    Comment #40465762

    Actually it means both, in an unfortunate case of term overload. Though I can understand the embedded/IoT world being frustrated by this, as the term existed first within that cont…

  7. comment
    Comment #40465747

    The edge within this context means running a server close, in terms of Internet latency, to users. For example, if a user if sending a request from Germany, then the response shoul…

  8. comment
    Comment #40465690

    Yes, though I'd like to point out that "scale to zero" is a loose definition to mean anything that can be transparently scaled to 0 whenever an app/service is idle, and then wake u…

  9. comment
    Comment #40465627

    100% agree. In almost all cloud deployment, whether transparently or not, you'll have a hypervisor/VM underneath for hardware-level/strong isolation reasons. Using wasm on top of t…

  10. comment
    Comment #40465525

    On kraft.cloud we can (done internal stress tests for this) run thousands of specialized VMs (aka unikernels) scaled to zero, meaning that when a request for one of them arrives we…

  11. comment
    Comment #40465502

    Hi, on kraft.cloud we use FC, along with a custom controller and very specialized VMs (unikernels) to have extremely efficient deployments (eg, millisecond cold starts). For a PHP …

  12. comment
    Comment #40463512

    Fully agree, doing reactive autoscaling when the actual boot time is slow is an inherently hard problem. We've done years of research into building specialized VMs (unikernels) and…

  13. comment
    Comment #40463471

    [Disclaimer: I'm with KraftCloud] For what it's worth, Firecracker/the VMM is only one part of the boot process. Among others, there's also the controller and the VM/OS itself that…

  14. comment
    Comment #40359370

    Author here, we did this, first by continuing the research alongside the creation of the Unikraft LF OSS project -- the result of which was the Eurosys 2021 best paper award ( http…

  15. comment
    Comment #40359343

    Hey, author/founder here, thanks for providing that answer, all correct there :) . I would also add that KraftCloud unikernels are built using Unikraft, and that its modularity all…

  16. comment
    Comment #40355178

    The 125ms is using Linux. Using a unikernel and tweaking Firecracker a bit (on KraftCloud) we can get, for example, 20 millis cold starts for NGINX, and have features on the way to…

  17. comment
    Comment #40355135

    Agree with epr's definition of a unikernel (and no, no mental decline on your part, this isn't always well defined). First off, a unikernel is a virtual machine, albeit a pretty sp…

  18. comment
    Comment #40355082

    The model of a single container within a VM just adds overhead. The ideal case would be to remove the container layer and have the application(s) within the container run directly …

  19. comment
    Comment #40355015

    [One of the authors of the paper] I wouldn't recommend writing a network stack from scratch, that is a lot of effort. Instead, with the Unikraft LF project (www.unikraft.org) we to…

  20. comment
    Comment #40354995

    [Author of the paper here] You hit the nail on the head, this is precisely what we do (kernel API compatibility) with the LF Unikraft project (the evolution of the 2017 paper) at w…

  21. comment
    Comment #40354933

    Correct, we never did release Tinyx, mostly because it was in a very unclean/researchy state = not ready for public consumption. In retrospect, we probably should have either (a) m…

  22. comment
    Comment #40354900

    Maybe try out kraft.cloud: we take Dockerfiles as input and automatically convert to lightweight VMs/unikernels when deploying (disclaimer: I'm one of the paper's authors and one o…

  23. comment
    Comment #40354735

    Yes, Kata started as clear containers. And yes, the main purpose is compatibility with containers -- though generally speaking, adding layers to the cloud stack never helps to make…

  24. comment
    Comment #40354704

    Back when we did the paper, Firecracker wasn't mainstream so we ended up doing a (much hackier) version of a fast VMM by modifying's Xen's VMM; but yeah, a few millis was totally f…

  25. comment
    Comment #40354633

    I agree with the other comments. On the cloud, the VM is still the golden standard for strong (hardware-level isolation): if you deploy a container in the cloud, you can almost be …