On Monday, April 22, 2013 7:28:30 AM UTC-7, Justin Lebar wrote: > > The issue isn't compilation of code; that doesn't stick out in the > memory reports. The issue seems to be mostly the overhead of the JS > engine for each file (even if the file stores very little data, as > BrowserElementParent does) and also the unavoidable inefficiency > associated with assigning each worker its own runtime (in particular, > the fact that this greatly increases fragmentation). >
Probably this doesn't make sense, but could some of the code running in JS workers be combined to live inside fewer actual workers? The main downside would be less concurrency obviously, but it sounds like it could avoid some memory overhead? - Alon _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
