That is what we are measuring indeed.
> But why would a user care about that metric rather than the total elapsed time?
Because that is the time where the user feels he has already done his part, but the site he is on is taking forever to do what he needs it to do.
Another reason why we measure the time from upload done to encoding done is because that's what our customers pay us to do.
So at some point in the future we'll offer upload servers in all major geographic areas.
Comcast used to route my traffic to California through Seattle, Washington, then down to San Jose and then Fremont, but now, it's going to Texas first, then across to San Diego, then up to Fremont, across a saturated link.
However, it wouldn't be particularly useful for things like queuing uploads from a directory. The point of NaCl is running native machine code in a provably secure sandbox. It's about making possible web app features faster on the client side, rather than adding new capability, per se.
"Since our servers can encode video much faster than most of your users can upload it, this means there is literally no more delay between the end of the upload and the video finishing encoding. In the screencast above this makes a 150x speed difference."
Surely the upper bound is 2x if you could transcode faster than the upload before.
Unless you are just measuring the time between the upload finishing and the transcode being done. But why would a user care about that metric rather than the total elapsed time?