Not really if you define (as Amazon would) efficiency as order throughput and cost-per-order. Humans are typically more expensive than robots per hour: robots cost upfront and then maintenance + energy, but if those sum up to an hourly rate beyond the cost of humans for a jobs that humans can do at comparable quality... you wouldn't have robots yet. Kiva exists and continues to get deployed...
To fulfill an order with Kiva, a human stands at a ship station (boxes, label printing, tape) near a fast path (door, belt) to outbound. Shelves are brought, the human picks the item from the shelves and assembles the order. That's putting the humans in the loop where robotics is harder/more expensive. Your hard fulfillment rate limit is then the time it takes the human to pick and assemble the order, plus whatever time it takes the robots to bring the shelves over. This scales gracefully (install more robots until the hard latency of order fulfillment becomes robot travel time from the farthest shelf to the human, plus human time) -- robots scale with the number of shelves, humans scale with the number of fulfillment stations.
To fulfill via Segway, you tie up a human for the entire travel time between station and the traveling salesman problem of order picking and back. Or you do as Amazon was doing in this article, and split pick and pack and allow for subdividing orders between pickers, and so on. This works (obviously) and the segway approach would likely improve fulfillment speed for pickers. But it does not save operating expense (headcount).
Recs (therecordstream.com) is great for this. A JSON log file would be interpreted as its native record format, so you can use all of its processing tools (like recs-grep and recs-collate and recs-sort).
This is nice, simple experiment design. However, I'm really surprised they only ran this once - or indicate trial counts and indicate range/distribution. I'd be curious if video transcoding is so consistent that a single measurement is enough to draw a conclusion; certainly network/storage transfer is not. Sure, time and bandwidth are not free...
Hi DMV - we ran the transcoding tests a few times, but transcoding performance is pretty steady across multiple runs (here and elsewhere).
Network obviously isn't; the numbers here include about a dozen test runs. We should make that more clear. Even a dozen isn't enough to be a scientific test, so hopefully we (or someone else) will do more benchmarking in the future.
The Tepper School of Business is a college at CMU just like the newly-named Marianna Brown Dietrich Humanities and Social Sciences college. The colleges contains departments such as English, Philosophy, etc.
If this is appealing, I recommend trying RecordStreams (http://code.google.com/p/recordstream/). I use it for ad hoc Big Data command line analysis almost daily.
Consider the MOTOFONE. Fancy e-Ink display, but has battery life measured in days. Designed for the third world market, it can text message... badly, and that's it beyond good call quality.
To fulfill an order with Kiva, a human stands at a ship station (boxes, label printing, tape) near a fast path (door, belt) to outbound. Shelves are brought, the human picks the item from the shelves and assembles the order. That's putting the humans in the loop where robotics is harder/more expensive. Your hard fulfillment rate limit is then the time it takes the human to pick and assemble the order, plus whatever time it takes the robots to bring the shelves over. This scales gracefully (install more robots until the hard latency of order fulfillment becomes robot travel time from the farthest shelf to the human, plus human time) -- robots scale with the number of shelves, humans scale with the number of fulfillment stations.
To fulfill via Segway, you tie up a human for the entire travel time between station and the traveling salesman problem of order picking and back. Or you do as Amazon was doing in this article, and split pick and pack and allow for subdividing orders between pickers, and so on. This works (obviously) and the segway approach would likely improve fulfillment speed for pickers. But it does not save operating expense (headcount).