475
edits
Electrolysis: Difference between revisions
Jump to navigation
Jump to search
→Goal: updated estimated delivery
(add triage list for perf) |
(→Goal: updated estimated delivery) |
||
| Line 3: | Line 3: | ||
The goal of the current Electrolysis project ("e10s" for short) is to render and execute web related content in a single background 'content' process which communicates with the main Firefox process via various [https://developer.mozilla.org/en-US/docs/IPDL ipdl protocols]. The two major advantages of this model are security and performance. Security improvements are accomplished through sandboxing, performance improvements are born out of the fact that multiple processes better leverage available client computing power. | The goal of the current Electrolysis project ("e10s" for short) is to render and execute web related content in a single background 'content' process which communicates with the main Firefox process via various [https://developer.mozilla.org/en-US/docs/IPDL ipdl protocols]. The two major advantages of this model are security and performance. Security improvements are accomplished through sandboxing, performance improvements are born out of the fact that multiple processes better leverage available client computing power. | ||
For current status, visit the current [[Electrolysis/Roadmap|project roadmap overview]]. The e10s team estimates e10s with a single content process will be enabled in Firefox Release by the | For current status, visit the current [[Electrolysis/Roadmap|project roadmap overview]]. The e10s team estimates e10s with a single content process will be enabled in Firefox Release by the middle of 2016. | ||
==Enabling and Disabling Electrolysis== | ==Enabling and Disabling Electrolysis== | ||