Hakuna Cloud – Stop cloud servers when they are not in use
1–10 of 64 posts
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#2No thank you.
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#3- Using the Kubernetes Vertical Pod Autoscaler (https://github.com/kubernetes/autoscaler/tree/master/vertica...) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling
- Collecting metrics on container CPU and memory allocation vs utilization
- Writing scripts to auto-submit PRs to SREs with better recommended sizing based on actual usage
- Tuning our VM instance sizes and autoscaler configs
A few engineers were able to save the company several times their salary with a few months of work, and plan to 10x the savings over the next year
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#4Efficiency is an area where there can be a lot of cost hiding. We recently saved a lot of money by: - Using the Kubernetes Vertical Pod Autoscaler ( https://github.com/kubernetes/autoscaler/tree/master/vertica... ) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling - Collecting metrics on container CPU and memory allocation vs utilization - Writin…
HakuaCloud starto&stop cloud servers, so you actually pay only for the time the servers are needed
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#5Also, how does hakuna work with DO? I thought DO still charges when VMs are powered off?
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#6Jokes aside, I wonder when cloud providers will add something like this as a native feature.
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#7Interesting idea. Almost bring the idea of lambda to VMs, doesn't it? Also, how does hakuna work with DO? I thought DO still charges when VMs are powered off?
With DO, we destroy the instance so that nothing is charged for it, and save a snapshot to be used to restart the instance; you pay only for the snapshot storage - $0.05/GB per month.
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#8> Each cloud server must have an FQDN/DNS name configured as a CNAME to our load balancers.
> When your server stops receiving requests, it will be stopped. As soon as a new request arrives, Hakuna will start it.
Interesting idea. It's like a proxy that kind of makes an instance/vm-based service act like a serverless service, without moving to containers or rewriting.
Seems kind of niche but I can see the use: there's a lot of services that have a time-based usage pattern (during working hours, or used interactively for a few minutes/hours sparsely through the day).
What are the cold start times like with this (at least for a typical, simple app - say on asp.net on Windows or something hosted via nginx on Linux)? What happens if an instance is being stopped and a new request comes in - does the request have to wait for shutdown plus startup?
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#9Efficiency is an area where there can be a lot of cost hiding. We recently saved a lot of money by: - Using the Kubernetes Vertical Pod Autoscaler ( https://github.com/kubernetes/autoscaler/tree/master/vertica... ) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling - Collecting metrics on container CPU and memory allocation vs utilization - Writin…