This topic has come up on es-discuss again[1], with Mark Miller referencing[2] an older post of his to the list that contains a proposal for mitigating the issues with making GCs visible[3].
[1]: https://mail.mozilla.org/pipermail/es-discuss/2013-November/034619.html [2]: https://mail.mozilla.org/pipermail/es-discuss/2013-November/034630.html [3]: https://mail.mozilla.org/pipermail/es-discuss/2013-January/028542.html On Mon, Nov 4, 2013 at 7:14 PM, Brendan Eich <bren...@mozilla.com> wrote: > Terrence Cole wrote: > >> Recently, Luke tried turning down the incremental slice time >> knob to see how low we could go. He found that2ms is easily doable, >> >> except when traversing the browser C++ heap, taking about6ms. >> > > I wonder how this scales on, say, a Nexus 4 (not to drag us all down to a > ZTE Open). Anyone know? > > > /be > _______________________________________________ > dev-tech-js-engine-internals mailing list > dev-tech-js-engine-internals@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
