Mobile/XULOptimization: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(New page: == Issues == == Goals == == Task list == === Bugs === === Features ===)
 
No edit summary
 
(2 intermediate revisions by 2 users not shown)
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 ===


=== Features ===
=== XUL Profiling ===
 
* Merged "reportLiveObjects" patch from timeless to trunk on 2/5/2008 and uploaded [http://wiki.mozilla.org/images/3/38/Peller_02052008.zip here]. The original patch is around 2 years old and could be found [http://www.webwizardry.net/~timeless/peller here].
* The current plan is to use this patch for profiling the XUL widgets.
* Output generated by "reportLiveObjects" patch
** [http://wiki.mozilla.org/images/3/3d/Xul_prof_startup.txt.zip Output after Browser startup]
** [http://wiki.mozilla.org/images/3/37/Xul_prof_all_bookmarks.txt.zip Output after opening Bookmarks -> Show all Bookmarks]

Latest revision as of 21:19, 11 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

Bugs

XUL Profiling