75
edits
Multiple content processes: Difference between revisions
Jump to navigation
Jump to search
windows cross process memory sharing API
(added links section) |
(windows cross process memory sharing API) |
||
| Line 9: | Line 9: | ||
[http://www.erahm.org/2016/02/12/are-they-slim-yet/ Memory usage of e10s compared to other browsers] gives us some breathing space. | [http://www.erahm.org/2016/02/12/are-they-slim-yet/ Memory usage of e10s compared to other browsers] gives us some breathing space. | ||
The challenge is to avoid the content processes allocating memory for the same resources. B2G is already using multiple content processes for apps, and solving this problem with [https://blog.mozilla.org/nnethercote/2014/02/11/nuwa-has-landed/ | The challenge is to avoid the content processes allocating memory for the same resources. B2G is already using multiple content processes for apps, and solving this problem with [https://blog.mozilla.org/nnethercote/2014/02/11/nuwa-has-landed/ Nuwa] which is based on copy-on-write forking mechanism that is provided by Linux. [https://msdn.microsoft.com/en-us/library/windows/desktop/aa366551(v=vs.85).aspx Windows have a quite different API to share memory between processes] and it has to be investigated if it's usable for Nuwa. [https://msdn.microsoft.com/en-us/library/windows/desktop/aa366551(v=vs.85).aspx Boost] uses this API for memory sharing. | ||
Another approach was suggested by Till Schneidereit [https://bugzilla.mozilla.org/show_bug.cgi?id=876173 lazy cross-process memory sharing]. | Another approach was suggested by Till Schneidereit [https://bugzilla.mozilla.org/show_bug.cgi?id=876173 lazy cross-process memory sharing]. | ||
We also want to monitor the resource usage of each | We also want to monitor the resource usage of each sub-process {{Bug|1255843}} which will open doors for further optimization strategies. | ||
== Process strategy == | == Process strategy == | ||