- From: Ben Kelly <notifications@github.com>
- Date: Fri, 10 Apr 2015 08:46:18 -0700
- To: whatwg/streams <streams@noreply.github.com>
Received on Friday, 10 April 2015 15:46:45 UTC
@yutakahirano its due to the async primitives the polyfil has available. It has to use something like setTimeout. Unfortunately, if you nest more than 4 or 5 setTimeout calls it will begin forcing the delay to a minimum of 4ms. This places the upper bound of an async loop like this at 250 ops/sec. In theory something like postMessage could avoid the 4ms clamping, but I think browsers have started doing it for nested postMessage recently as well. The polyfil needs something like node's nextTick to perform well on this test. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/320#issuecomment-91597727
Received on Friday, 10 April 2015 15:46:45 UTC