Re:Zerg: Boot a VM instance per request, all in under 250 ms
by AdamJacobMuller on Thursday December 28, 2017 @12:06AM
(#16020431)
Did they just inadvertently point out why this is a bad idea for anything general-purpose?
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by derefr on Thursday December 28, 2017 @12:11AM
(#16020443)
Not really; those are exactly the sort of config settings you'd sensibly use to prevent someone from DDoSing your untrusted prototype-level infrastructure.
If your VMs are truly cheap, and you've ironed out the kinks from your proof-of-concept, you'd obviously set up your production system to run more than 16 of them.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by StreamBright on Thursday December 28, 2017 @09:22AM
(#16022099)
Right, and who decides that a request coming from a customer ot an attacker? If the attacker can generate enough requests non of the customers have a chance to use your service. This is absolutely not the way to handle DDoS.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by derefr on Thursday December 28, 2017 @08:35PM
(#16026827)
My point was that it's a sensible strategy for the demo of a technology that's still under development (like this project), where you don't actually have any "customers." In production, you'd let it scale unboundedly, and combine it with some sort of anti-DDoS technology like Cloudflare.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by rozap on Thursday December 28, 2017 @12:43AM
(#16020547)
The point is to show boot times. If you are scaling up/down in response to load, this is a nice quality to have. Most folks have really spiky traffic patterns so this can save you a lot of money.
Obviously no one would ever run something like this 1 vm per request thing irl.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by notzorbo3 on Thursday December 28, 2017 @03:38AM
(#16020996)
> Obviously no one would ever run something like this 1 vm per request thing irl.
I can see plenty of use-cases for doing just that. Large uploads, time-consuming request/responses such as server-side data processing, RPC, as a backend behind a caching front-end so that it only has to respond to invalidated cache entries, etc.
I don't see many people using this to actually serve general website requests though. It'd probably be modified to serve multiple requests until nothing is left to do and then exit.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by ComodoHacker on Thursday December 28, 2017 @12:52AM
(#16020573)
Never say never...
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by Dylan16807 on Thursday December 28, 2017 @12:13AM
(#16020452)
It depends on how many resources it takes to run those 16 instances. If it's an extremely small demo allocation, then that's not a big deal. If it's multiple gigabytes and cores then the efficiency is awful.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by robert-boehnke on Wednesday December 27, 2017 @11:31PM
(#16020315)
They should spawn more overlords instead.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by daodedickinson on Thursday December 28, 2017 @02:05AM
(#16020779)
We require more mineralsssss
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by sova on Wednesday December 27, 2017 @11:32PM
(#16020318)
You have not enough Vespene Gas
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by tfcata on Wednesday December 27, 2017 @11:39PM
(#16020342)
Overlords only need mineral, 100 each.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by sova on Wednesday December 27, 2017 @11:43PM
(#16020354)
You're right. Mea culpa, I always played Protoss.
Re:Zerg: Boot a VM instance per request, all in under 250 ms
by keeganpoppen on Wednesday December 27, 2017 @11:56PM
(#16020403)
in case you haven’t already noticed, hacker news is not a place for jokes...
> The demo is limited to 16 concurrent instances and 2 libvirt connections. Due to these limitations we were unable to spawn a new instance to service your request. Please try again later.
Kool.