Mobile/XULOptimization: Difference between revisions
< Mobile
Jump to navigation
Jump to search
(New page: == Issues == == Goals == == Task list == === Bugs === === Features ===) |
No edit summary |
||
| Line 1: | Line 1: | ||
== Issues == | == Issues == | ||
XUL requires significant memory. On the N800, trunk Firefox with the standard chrome requires ~10MB RAM on startup, and this reduces to ~6.5MB with a simpler chrome. This indicates significant RAM use by XUL. | |||
== Goals == | == Goals == | ||
Reduce startup RAM requirement to ~5 MB on the N800. This matches the Maemo browser's RAM needs on startup. | |||
== Task list == | == Task list == | ||
* Profile individual XUL widgets -- avoid expensive XUL widgets in Mobile Chrome | |||
* Optimize XPCOM objects used by XUL widgets | |||
=== Bugs === | === Bugs === | ||
Revision as of 16:42, 4 February 2008
Issues
XUL requires significant memory. On the N800, trunk Firefox with the standard chrome requires ~10MB RAM on startup, and this reduces to ~6.5MB with a simpler chrome. This indicates significant RAM use by XUL.
Goals
Reduce startup RAM requirement to ~5 MB on the N800. This matches the Maemo browser's RAM needs on startup.
Task list
- Profile individual XUL widgets -- avoid expensive XUL widgets in Mobile Chrome
- Optimize XPCOM objects used by XUL widgets