Well, if we do not want the main thread to collapse under its weight, we have to move code off the main thread and to encourage add-ons to do likewise.
I'm not sure I see an alternative here. Cheers, David On 5/24/13 1:12 AM, Jonas Sicking wrote: > My main concern is that Workers created by Gecko are really expensive > memory-wise. See the thread started by Justin Lebar titled "Rethinking > the amount of system JS we use in Gecko on B2G". > > The short of it is that each Worker requires a separate JS Runtime and > we simply haven't optimize runtimes for having lots of them. This is > especially a problem for B2G where we are very short on memory and > where we are running multiple copies of Gecko. > > I would expect the same thing to be an issue on Firefox for Android, > though maybe less so since we're generally running on higher-end > hardware with more memory. > > So creating Workers from frontend desktop-only code seems fine. But > it's something that would worry me if we start doing in cross platform > Gecko code. > > / Jonas > -- David Rajchenbach-Teller, PhD Performance Team, Mozilla _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
