> Frankly I fail to see how this matters today or what kind of app he envisions where it could matter in the future.
> After all I cannot imagine a traffic pattern that would "flicker" at a second or even subsecond rate.
The app he's describing in the article: testing of his product. If done on 400 machines in parallel, it would take 2 min 36 sec, or 1.040 machine minutes. But he don't want to pay for 24.000 machine minutes, so he's opting for the the closer to one hour option, saving a lot of money, but failing at his objective: make the deployment (of which testing is a sub-process) as short as possible.
> After all I cannot imagine a traffic pattern that would "flicker" at a second or even subsecond rate.
The app he's describing in the article: testing of his product. If done on 400 machines in parallel, it would take 2 min 36 sec, or 1.040 machine minutes. But he don't want to pay for 24.000 machine minutes, so he's opting for the the closer to one hour option, saving a lot of money, but failing at his objective: make the deployment (of which testing is a sub-process) as short as possible.