11–20 of 29 posts
Earlier quoted context omitted.
Do you mean CUDA API hijacking?
not necessarily -- CUDA produces many function calls, which in API remoting setups could degrade performance -- in our case, we draw the abstraction line a bit "higher" in the stack so it's more like a "functional" API remoting -- eg. image classification
1- Is there an option to run your own "kraftcloud" in your own cloud account?
2- How does this compare to companies leveraging eBPF to squeeze more performance from the Kernel?
This looks amazing. 1- Is there an option to run your own "kraftcloud" in your own cloud account? 2- How does this compare to companies leveraging eBPF to squeeze more performance from the Kernel?
1. Yes. We're essentially a baremetal solution. Either we run it on your behalf (this is kraft.cloud), or we deliver an ISO or AMI and this can be installed on-prem/cloud-prem. This latter solution is our enterprise offering.
2. eBPF used in this way, I feel, has become a symptom of the problem that we're trying to solve at Unikraft: the bloated Linux- (and cloud native-) stack. In the end, you're adding more tools or doing more tricks to try and do computationally less since performance and running faster is about performing less operations in the critical-path. Unikraft approaches the problem space differently: bottom up (app first, then dependencies, then select OS libraries/primitives based on required syscalls) as opposed to top-down (taking away from Linux, its distros, removing functionality, making short-cuts, etc.).
Looks awesome! Trying to use it for a toy project, I realized you almost always need some persistence layer. I see you support volumes and you have some guides about deploying databases. How does that work? Are they also "scale to zero"? Why is Postgres special? Referring to the "contact us" mention. Or if I want to "bring my own DB", what are the latencies to other providers? Can I somehow host a DB in the same data…
Because KraftCloud leverages Unikraft, a unikernel library OS project, we are single-process. Postgres is multi-process since it uses the fork() syscall. If you require Postgres, we can set it up for you as a managed service. That said also, we are currently working on supporting fork() and this should become available in the next few weeks/end of April.
Re: bring your own DB: yes. We are setting up metros in many popular hyperscalers and IaaS vendors and DC zones. This means there should be no egress fees and you'll have data locality.
For serious deployments, be close to your data. If you get in contact (alex@unikraft.io), we can discuss further how we are approaching this.
And yes, we are working on cron, this will translate to setting up an instance to start at a regular interval and not auto-restart it (so it scales-to-zero). :-)
Would this work for hosting databases too? I found the biggest annoyance and expense on my "infrequently accessed" side projects are databases, which are almost always idle.
Looks great! Would this work for hosting databases too? I found the biggest annoyance and expense on my "infrequently accessed" side projects are databases, which are almost always idle.
We have a whole section in our documentation's guides section on example usecases with database:
https://docs.kraft.cloud/guides/#databases
They work exactly as you suggest, they scale-to-zero when no requests are made and data can be safely stored/transactioned in persistent volumes on the platform too.
Looks great! Would this work for hosting databases too? I found the biggest annoyance and expense on my "infrequently accessed" side projects are databases, which are almost always idle.
Thanks and, yes it does! We have a whole section in our documentation's guides section on example usecases with database: https://docs.kraft.cloud/guides/#databases They work exactly as you suggest, they scale-to-zero when no requests are made and data can be safely stored/transactioned in persistent volumes on the platform too.
Both the twitter above and the HN user posted the link to findtime.fberge.com
Note everyone it's probably a big coincidence! These two posters most likely do not know each other. This exchange is totally legit.
You should seriously consider a pay as you go plan that bills by minutes or some metric. This is actually what I was expecting when I went to pricing.
Their FAQ says 1. Scale-to-Zero: don’t ever pay for idle again; So I believe this is true? Where are you seeing a pricing page anyway?