Confirmed users
2,492
edits
(→Status) |
(→Goals) |
||
| Line 14: | Line 14: | ||
There are number of things we believe the e10s project will give us (ordered in relative priority). | There are number of things we believe the e10s project will give us (ordered in relative priority). | ||
1. Better overall application UI responsiveness. | |||
2. Improved performance, especially on multi-core machines. | |||
3. Better memory core stats. | |||
4. Using more than 1 content process. | |||
5. Crash protection. A web content crash doesn't take down the entire browser. | |||
6. Preparation for sandboxing. Web content can be sandboxed more cleanly. | |||
** A goal for the security team is to prepare a threat model for e10s. | ** A goal for the security team is to prepare a threat model for e10s. | ||
7. Add ons/extensions (need a crisp goal defined here) | |||
The #1 driver for e10s is to improve the application responsiveness, or the perception thereof. | The #1 driver for e10s is to improve the application responsiveness, or the perception thereof. | ||
Other interesting gains but not explicit goals... | Other interesting gains but not explicit goals... | ||
* Better visibility into how resources are being used. | * Better visibility into how resources are being used. | ||