[whatwg/streams] Latency-bounded reads (Issue #1270)

Many media-related use cases complain that there's a lot of overhead from unnecessary wakeups from `read()`, as streaming network reads use too much CPU and power. They would benefit from latency-bounded reads i.e. "try to fulfill read() once, 10ms from now, with all the data you've received between now and then".

In addition to `min` in https://github.com/whatwg/streams/pull/1145, it might be good to have something like `deadline` as an option for `read()` to allow for latency-bounded reads.

cc @ricea 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1270
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/streams/issues/1270@github.com>

Received on Friday, 7 April 2023 13:25:40 UTC