David Bruant wrote:
Article version and longer talk at
http://www.html5rocks.com/en/tutorials/memory/effectivemanagement/
Thanks.
They showed historical plots revealing gmail bugs, V8 GC regressions,
all the interesting dirt. Their tooling is great
I wouldn't say "great". It's state-of-the-art in web development, it's
the best things we have so far, but I still find the tool very hard to
use and
You're right, I should leave superlatives to their marketing. It's all
relative => standards are low :-P. Good news: we can do better in
Firefox DevTools. Thanks for your help there.
But when they called on JS developers to manage GC pause time, they
lost me.
How are JS developers supposed to manage pause time, even indirectly
(by avoiding unnecessary allocations and fixing leaks)? There's no
way. We won't be adding manually callable gc() built-ins to the
standard.
They seem to take their experience with V8 as a generality. I think
what they meant was that allocating triggers GC which triggers copying
(compacting?), which costs, so be careful with allocations. But this
advice is hard to follow in practice.
It is useless advice.
Can we learn from pause-free or realtime GC work, e.g. Metronome by
David Bacon et al. at IBM Research?
/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
