On Mon, Mar 6, 2017 at 7:29 PM, Ben Kelly <bke...@mozilla.com> wrote:
> In general I think processes that rely on native code vs chrome script will > do better here. My impression is that the chrome script js heaps make it > more difficult for the processes to share memory compared to native code > pages. I could be wrong, though. > I took some measurements last June [1] based on some earlier ones Eric and Nick did. About half the overhead in content processes comes from JS. The next biggest bucket is heap-unclassified. More concretely, our content process overhead at that time was 22MB, and about 10MB of that was JS. So 12MB is probably an upper bound on the overhead for things like the GPU and GMP processes. -Bill [1] https://docs.google.com/document/d/1Q6Cs2kEbVaB0hkXq40nsBK3EFCsT-ZxERIkPIJyya0s/edit?usp=sharing > > Ben > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
