6 ms·
Really welcome, although per millisecond would be better. It's now possible to boot operating systems in milliseconds and have them carry out a task (for examp
by andrewstuart 9y ago
Really welcome, although per millisecond would be better.
It's now possible to boot operating systems in milliseconds and have them carry out a task (for example respond to a web request) and disappear again. Trouble is the clouds (AWS, Google, Azure, Digital Ocean) do not have the ability to support such fast OS boot times. Per second billing is a step in the right direction but needs to go further to millisecond billing, and clouds need to support millisecond boot times.
- jawns 9y agoSounds like you're describing AWS Lambda / serverless architecture. But maybe I'm not understanding your use case?
- andrewstuart 9y agoThere are a wide range of tiny operating systems that can boot in a matter of milliseconds. The applications are "whatever you want imagine" but yes one application is building FAAS Function As A Service in which the operating system carries out a single function. Put anther way, Docker is complex, overweight, and requires re-implementation of much computing infrastructure. You can meet many of the same goals as Docker in much more simple way not by building containers but by building tiny operating systems.
- jpatokal 9y agoI'm somewhat amused by the idea of booting an operating system from scratch to service a single request being described as "much more simple" than the alternative of, y'know, having a single instance serve many requests.
- deleted 9y ago[deleted]
- icebraining 9y agoDocker is just a manager of Linux namespaces. You'll need one to manage your operating systems anyway - start/stop them, copy them to the machine, delete them, etc.
- mritun 9y agoOS does not serve requests -- applications do. While it may be possible to demo a toy OS+app, real-world applications take seconds if not minutes to start and warm up. Throughput on a cold-cache is a fraction of that on a warm cache. Starting in milli-seconds is not the hard problem. Starting + warming caches in that time is -- that will get you a bunch of awards when you solve it.
- Twirrim 9y agoFrom an ops perspective, spinning up an instance to process a single request seems like 1) a complete and utter nightmare to debug. 2) A huge waste of computing resources. Even with a unikernel you're wasting time initialising resources and getting in to a ready state to be able to process a request. Why bother when you can be ready and respond effectively instantly?
- planteen 9y agoJust curious here, what OS can do millisecond boot times? How many milliseconds are you talking? And the constant boot time of the OS is so much less than the OS responding to the web request that this is actually worth it?
- tylerhou 9y agohttps://en.wikipedia.org/wiki/Unikernel https://en.wikipedia.org/wiki/Unikernel
- planteen 9y agoIntersting. There's a link to here on the Wikipedia page: http://zerg.erlangonxen.org/ http://zerg.erlangonxen.org/ But if I'm reading things correctly, it still took over two orders of magnitude longer to boot than it did to reply. So what sort of use case does millisecond boot help with? Very sporadic requests?
- jopsen 9y agoCold EBS boot will still be super slow...
- vidarh 9y agoIf you're concerned about cost, AWS is almost never the right place to host to begin with.
- prohor 9y agoAgreed - just check cloud comparison, AWS is rarely at the top: https://www.cloudorado.com/cloud_server_comparison.jsp https://www.cloudorado.com/cloud_server_comparison.jsp
- xref 9y agothat's a very handy site, previously I had mostly been using http://www.ec2instances.info/ http://www.ec2instances.info/ and http://www.gceinstances.info/ http://www.gceinstances.info/ Thanks for pointing it out!
- whoisjohnkid 9y agoWow thanks for sharing this link. Didn't know about this. One thing I noticed though is the pricing seems a bit biased; for example for AWS it recommends an m1.small with 1GB Ram and 20GB of Storage at $35 a month ... However if you used a t2.micro that would give you the same specs for $10.79
- chillydawg 9y agoNot quite the same, you don't own the whole core on the t2 and will get cpu throttled.
- vacri 9y ago> you don't own the whole core Moving the goalposts here. 'Not owning the whole core' is the default in the cloud.
- vidarh 9y agoFor the other instances you get a specific number of units of processing capacity that you can use 100% of continuously if you like. For the micro instances, you get a base level and build up credits towards bursts, and can not maintain 100% utilization continuously. It's very much different and not the default. To quote Amazon: > "A CPU Credit provides the performance of a full CPU core for one minute. Traditional Amazon EC2 instance types provide fixed performance, while T2 instances provide a baseline level of CPU performance with the ability to burst above that baseline level. The baseline performance and ability to burst are governed by CPU credits." A t2.micro allows only 10% of the vCPU baseline performance. Anything above that needs to be "earned" at a rate of 6 credits per hour. The t2.micro can accumulate a maximum of 144 CPU credits (+ the 30 initial credits, that do not renew), each good for 1 minute of 100% use. So in other words, you can on average only use 100% of the CPU for 6 minutes per hour.