- From: Rick Waldron <waldron.rick@gmail.com>
- Date: Fri, 4 Jul 2014 20:15:44 -0400
- To: Fabrice Desré <fabrice@mozilla.com>
- Cc: public-device-apis <public-device-apis@w3.org>
Received on Saturday, 5 July 2014 00:16:38 UTC
On Fri, Jul 4, 2014 at 6:00 PM, Fabrice Desré <fabrice@mozilla.com> wrote: > On 07/04/2014 12:25 PM, Domenic Denicola wrote: > > Rick, Chromium has a multi-process architecture, whereas Firefox in > > general keeps most things in a single process. Thus Firefox has the > > ability to implement many more things synchronously than Chromium does. > > Implementation experience based on a single vendor is not terribly > > valuable in guiding API surface, especially in questions of sync vs. > > async, and especially when that vendor is Firefox (the only > > single-process modern browser, from what I understand). > > FirefoxOS/b2g is multi-process too, so we care a about not doing undue > sync IPC. We are doing some for the battery (see > https://mxr.mozilla.org/mozilla-central/source/hal/sandbox/PHal.ipdl#109). > I can run some timings if people are interested in knowing how long we > are blocked in these calls. > I went ahead and did some basic timing measurements on both device (FirefoxOS 1.4 [Fx30], ZTE Open) and desktop (Firefox 30, OSX 10.9.3). I reviewed the timing method and results with Fabrice to confirm correctness. https://gist.github.com/rwaldron/850590359d298e35bc61 Rick
Received on Saturday, 5 July 2014 00:16:38 UTC