<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.mozilla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ErinLancaster</id>
	<title>MozillaWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.mozilla.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=ErinLancaster"/>
	<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/Special:Contributions/ErinLancaster"/>
	<updated>2026-04-15T09:56:49Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.10</generator>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox/Planning/2011-09-28&amp;diff=352475</id>
		<title>Firefox/Planning/2011-09-28</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox/Planning/2011-09-28&amp;diff=352475"/>
		<updated>2011-09-28T17:23:18Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* The bigger issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Planning Meeting Details&#039;&#039;&#039;&lt;br /&gt;
* Wednesdays - 11:00am PDT, 18:00 UTC&lt;br /&gt;
* Mountain View Offices: Warp Core Conference Room&lt;br /&gt;
* Toronto Offices: Fin du Monde Conference Room&lt;br /&gt;
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel&lt;br /&gt;
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Video/Teleconference Details - NEW&#039;&#039;&#039;&lt;br /&gt;
* 650-903-0800 or 650-215-1282 x92 Conf# &#039;&#039;&#039;95312&#039;&#039;&#039; (US/INTL)&lt;br /&gt;
* 1-800-707-2533 (pin 369) Conf# &#039;&#039;&#039;95312&#039;&#039;&#039; (US)&lt;br /&gt;
* Vidyo Room: Warp Core&lt;br /&gt;
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&amp;amp;key=UK1zyrd7Vhym Guest URL]&lt;br /&gt;
&lt;br /&gt;
{{Notes}}&lt;br /&gt;
&lt;br /&gt;
__FORCETOC__&lt;br /&gt;
&lt;br /&gt;
== Actions from Last Week ==&lt;br /&gt;
&lt;br /&gt;
* Sheila to come back on {{bug|687991}} -- crashes on alice.it without stack&lt;br /&gt;
** Fixed another bug so we could get the crash reports. Crash only showing in builds from 20110923 or earlier so appears fixed by {{bug|687768}}.&lt;br /&gt;
* Johnath to ping JB about Thunderbird participation in this meeting&lt;br /&gt;
** Sent mail, they are going to participate, but are going to lurk for a few weeks first (hi tbirders!)&lt;br /&gt;
* Johnath to ping Todd about apps participation in this meeting&lt;br /&gt;
** Sent mail...&lt;br /&gt;
&lt;br /&gt;
== Schedule &amp;amp;amp; Progress on [[Releases|Upcoming Releases]] ==&lt;br /&gt;
&lt;br /&gt;
===Firefox Desktop ===&lt;br /&gt;
==== Release (3.6, 7) ====&lt;br /&gt;
&lt;br /&gt;
==== Beta (8) ====&lt;br /&gt;
&lt;br /&gt;
==== Aurora (9) ====&lt;br /&gt;
* We got some really nice capabilities uplifted from m-c to Aurora yesterday. Here&#039;s a taste.&lt;br /&gt;
** &amp;quot;Type Inference&amp;quot; giving us up to 44% performance improvements on AWFY&lt;br /&gt;
** Twitter Search&lt;br /&gt;
** &amp;quot;Two-finger swipe for Lion&amp;quot; for back and forward navigation on Mac 10.7 Lion.&lt;br /&gt;
** &amp;quot;New Lion-ized theme for Lion&amp;quot; toolbars, icons, buttons, etc.&lt;br /&gt;
** Tweaks to the Windows theme for Win7 consistency&lt;br /&gt;
** You can now create bookmarks by dragging text URLs to bookmarks toolbar&lt;br /&gt;
** Now you can drag a link from another app and just drop it on Firefox and it will load&lt;br /&gt;
** &amp;quot;Always restore pinned tabs&amp;quot; No matter what the users settings for restoring tabs (or not) the App Tabs should always be restored.&lt;br /&gt;
** &amp;quot;Improve responsiveness of history removals&amp;quot;  deleting large numbers of history items from the Library view used to hang the browser forever. now it is much faster.&lt;br /&gt;
** &amp;quot;Add support for fave icons on jump list uri entries&amp;quot;  Windows 7 JumpLists, a pretty important windows integration feature, just got a lot better. Right click on Firefox in the taskbar and see the beautiful icon-ified jumplist popup.&lt;br /&gt;
** &amp;quot;should be able to reset a resized textarea&amp;quot;  Users can resize text areas in Firefox. If you resize a textarea and then double click on the resizer it will reset to the original dimensions. &lt;br /&gt;
** &amp;quot;Sync should never complain about a network problem anymore unless you the Sync Now menu item/toolbar button is clicked.&amp;quot; Sync is getting less noisy with its errors.&lt;br /&gt;
**  &amp;quot;Implement font-stretch property&amp;quot; was completed in 9.  It&#039;s notable because it was filed in 1999 :-)&lt;br /&gt;
** &amp;quot;add mouseenter and mouseleave DOM events&amp;quot; high-profile web devs have been begging for this for a good while.&lt;br /&gt;
** &amp;quot;Implement CSS3 columns shorthand&amp;quot; CSS 3 columns are more important than ever and with IE 10 (and Windows 9) adding support for multi-column layout, we&#039;re finally getting there with colums.&lt;br /&gt;
** &amp;quot;Implement CSS3 text-overflow: &amp;lt;left&amp;gt; &amp;lt;right&amp;gt;&amp;quot;&lt;br /&gt;
** &amp;quot;API for controlling fullscreen from content&amp;quot; (still preffed off.)&lt;br /&gt;
** &amp;quot;Implement temporal dimension portion of Media Fragments URI specification for video/audio&amp;quot; This is kind of a huge step for Open Video.&lt;br /&gt;
&lt;br /&gt;
==== Nightly (10) ====&lt;br /&gt;
* The last week of trunk development was pretty great. Most of this made the uplift to Aurora as well.&lt;br /&gt;
** Bug 635645 - consider increasing the amount of scrolling performed by using the arrow keys -- This makes us scroll fast like all the other browsers. Easy win on perceived performance.&lt;br /&gt;
** Some nice tweaks to from front-end folks&lt;br /&gt;
*** Bug 684450 - Remove stop/go/reload button affordance and streamline other location bar icons&lt;br /&gt;
*** Bug 689051 - drop the drop shadow on the back button for Windows 7&lt;br /&gt;
*** Bug 632365 - Delay status updates for links further&lt;br /&gt;
*** Bug 462117 - Add specialized video controls for small-dimension media.&lt;br /&gt;
*** Bug 472942 - VideoDocument should center video in tab&lt;br /&gt;
&lt;br /&gt;
=== Firefox Mobile  ===&lt;br /&gt;
&lt;br /&gt;
==== The bigger issues ====&lt;br /&gt;
* Will Java front-end be feasible? Doug T. is driving toward an initial pros/cons analysis over the next week&lt;br /&gt;
* Flash support will land on nightly in the next few days, need to evaluate and set criteria for whether it would be good enough to ship (Note, this is smartphones only, because it&#039;s Gingerbread and earlier, not Honeycomb)&lt;br /&gt;
* Startup shrink continues and the focus is to get us ready for toronto work week. We&#039;re capturing baseline measurements for mem usage and responsiveness so that we can track optimization wins. We are also looking at analysis of metrics across release channel builds.&lt;br /&gt;
&lt;br /&gt;
==== 7 ====&lt;br /&gt;
* Released to Android market&lt;br /&gt;
* Ad-Block plus is likely the only major add-on affected by &amp;quot;hidden&amp;quot; add-on issue, no plan (let&#039;s discuss) to revert to 6.0.&lt;br /&gt;
* Reminder: Key Features in this release&lt;br /&gt;
** Copy &amp;amp; Paste&lt;br /&gt;
** Added a ‘Quit’ action to the Android menu&lt;br /&gt;
** Language detection on first-run&lt;br /&gt;
** Improved image rendering on Tegra-based tablets and phones (see bug 669851)&lt;br /&gt;
** The WebSocket API is now available in Firefox for Android (see bug 537787)&lt;br /&gt;
&lt;br /&gt;
==== 8 ====&lt;br /&gt;
&lt;br /&gt;
==== 9 ====&lt;br /&gt;
&lt;br /&gt;
* Major tablet UX refresh&lt;br /&gt;
* Webapps support&lt;br /&gt;
* More locale picker work&lt;br /&gt;
* Camera &lt;br /&gt;
* Need to make decisions on:&lt;br /&gt;
** Flash on demand (front-end patch getting better)&lt;br /&gt;
** UA&lt;br /&gt;
** Featurettes, like the Clear Private Data changes (need to triage)&lt;br /&gt;
&lt;br /&gt;
===Firefox Sync===&lt;br /&gt;
* Fx7 - [[Firefox/Features/Instant_Sync|Instant Sync]] &lt;br /&gt;
* Beta (8) - [[Firefox/Features/Instant_Sync|Instant Sync]] - remaining piece&lt;br /&gt;
** Relanded Drop single DeviceInterval to 1 hour. See  {{bug|678588}} and crash bug {{bug|598774}} for more info.&lt;br /&gt;
* Firefox 10+:&lt;br /&gt;
** [[Services/Sync/Sync_Setup_Improvements_Desktop|Improving Sync Set Up]] - In development&lt;br /&gt;
** [[Services/Sync/Push_to_device|Push to Device]] - In development. You can play with an add-on [https://addons.mozilla.org/en-US/firefox/addon/send-tab-to-device/ here].&lt;br /&gt;
** [[Services/Sync/Addon_Sync|Addon Sync]] - In development.&lt;br /&gt;
&lt;br /&gt;
===[[AMO/FlightDeck/0.9.7|Add-on Builder]]===&lt;br /&gt;
&lt;br /&gt;
=== Add-on SDK ===&lt;br /&gt;
&lt;br /&gt;
Release (1.1 -&amp;gt; Firefox 7)&lt;br /&gt;
&lt;br /&gt;
* 1.0 -&amp;gt; 1.1 repack occurred Monday, September 26&lt;br /&gt;
* repack process experienced some problems; they have now been resolved&lt;br /&gt;
* repack post-mortem to take place this week or next&lt;br /&gt;
&lt;br /&gt;
Stabilization (1.2 -&amp;gt; Firefox 7, 8)&lt;br /&gt;
&lt;br /&gt;
* second test build, 1.2b2, spun yesterday, Tuesday, September 27 ([https://groups.google.com/forum/#!topic/mozilla-labs-jetpack/7ZnM34nwpJM announcement])&lt;br /&gt;
* final release on schedule for Tuesday, October 25, two weeks before Firefox 8&lt;br /&gt;
* will probably move up final release one week to Tuesday, October 18, three weeks before Firefox 8 ([https://groups.google.com/forum/#!topic/mozilla-labs-jetpack/e0RkE4zW9ew discussion])&lt;br /&gt;
&lt;br /&gt;
Development (1.3 -&amp;gt; Firefox 8, 9)&lt;br /&gt;
&lt;br /&gt;
* merge to stabilization branch on schedule for Tuesday, October 25&lt;br /&gt;
* will probably move up merge and final release one week to ship three weeks before Firefox 9&lt;br /&gt;
&lt;br /&gt;
== Feedback Summary  ==&lt;br /&gt;
=== Desktop ===&lt;br /&gt;
Got a little busy with 7.0.1 so here&#039;s a copy-paste of the note I sent to rrrt last night:&lt;br /&gt;
&lt;br /&gt;
*Broken extensions:&lt;br /&gt;
**Yahoo Toolbar is a big one, apparently bookmarks stored there are wiped out entirely. Lots of complaints of dataloss here. (May also be bug 680802)&lt;br /&gt;
**One or two people saying noscript went missing (that&#039;s bug 680802).&lt;br /&gt;
**Lots of complaints about Norton toolbar -- [http://community.norton.com/t5/Norton-Internet-Security-Norton/Firefox-7-0-Compatibility-Patch-is-now-available/td-p/547384 Users have to update via Norton first before updating Firefox.]&lt;br /&gt;
**Kaspersky doesn&#039;t work at all.&lt;br /&gt;
**Java console also making a reappearance.&lt;br /&gt;
**1Password - From kev &amp;quot;1Password switched to a full JS implementation a while back. Users have been reluctant (from what I understand) to upgrade because there&#039;s some functionality loss.&amp;quot;&lt;br /&gt;
**Some banking extension (maybe trusteer)&lt;br /&gt;
**Roboform (also lots of complaints)&lt;br /&gt;
*Spike in people saying they lost bookmarks/favorites -- may be Yahoo toolbar. I know people about two weeks ago were saying that we &amp;quot;forced Yahoo on them&amp;quot; so I&#039;m not sure what&#039;s going on and Yahoo may have eaten the bookmarks. Or it can be the usual upgrade = profile loss.&lt;br /&gt;
*Firefox not responding randomly. (May be bug 686025 but triggered by the update or some users are saying that they are updating directly from 5 because of this problem but it&#039;s back.)&lt;br /&gt;
*Lost sessions (but we see this with almost every update) -- may be worse this time but hard to say.&lt;br /&gt;
*A few complaints about the missing http (not a lot... but some comments that it broke intranet pages and general whining)&lt;br /&gt;
*Maybe something about Yahoo mail layouts being screwed up (can&#039;t reproduce here.)&lt;br /&gt;
&lt;br /&gt;
=== Mobile ===&lt;br /&gt;
&lt;br /&gt;
== UX &amp;amp; User Research ==&lt;br /&gt;
&lt;br /&gt;
Tablet UI exploration (aka usability testing) to take place in Toronto during mobile work week (most likely Oct 18-19th). User research (aka Mary T) is looking for a developer or two to sit in on these sessions.&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Market Insights&#039;&#039;&#039;  ==&lt;br /&gt;
&lt;br /&gt;
A [http://src.chromium.org/viewvc/chrome?view=rev&amp;amp;revision=102140 fix landed] in Chromium to synchronise extension settings.&lt;br /&gt;
&lt;br /&gt;
Amazon announced the Silk Browser for the new [http://www.youtube.com/watch?v=_u7F_56WhHk Kindle Fire] tablet.&lt;br /&gt;
&lt;br /&gt;
Rockmelt announced that they will support [http://blog.rockmelt.com/post/10524740964/coming-soon-rockmelt-beta-4-brings-the-ultimate-reading Facebook OpenGraph] in the Beta product in a few weeks.&lt;br /&gt;
&lt;br /&gt;
== Marketing, Press &amp;amp;amp; Public Reaction  ==&lt;br /&gt;
&lt;br /&gt;
== Questions, Comments, FYI ==&lt;br /&gt;
&lt;br /&gt;
== Actions this week ==&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Firefox/Planning/2011-09-28&amp;diff=352474</id>
		<title>Firefox/Planning/2011-09-28</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Firefox/Planning/2011-09-28&amp;diff=352474"/>
		<updated>2011-09-28T17:22:53Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* The bigger issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&amp;lt;center&amp;gt;[[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Firefox/DeliveryMeetings|index]] | [[Firefox/Planning/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Planning Meeting Details&#039;&#039;&#039;&lt;br /&gt;
* Wednesdays - 11:00am PDT, 18:00 UTC&lt;br /&gt;
* Mountain View Offices: Warp Core Conference Room&lt;br /&gt;
* Toronto Offices: Fin du Monde Conference Room&lt;br /&gt;
* [irc://irc.mozilla.org/planning irc.mozilla.org #planning] for backchannel&lt;br /&gt;
* (the [[Platform#Meetings|developer meeting]] takes place on Tuesdays)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Video/Teleconference Details - NEW&#039;&#039;&#039;&lt;br /&gt;
* 650-903-0800 or 650-215-1282 x92 Conf# &#039;&#039;&#039;95312&#039;&#039;&#039; (US/INTL)&lt;br /&gt;
* 1-800-707-2533 (pin 369) Conf# &#039;&#039;&#039;95312&#039;&#039;&#039; (US)&lt;br /&gt;
* Vidyo Room: Warp Core&lt;br /&gt;
* Vidyo [https://v.mozilla.com/flex.html?roomdirect.html&amp;amp;key=UK1zyrd7Vhym Guest URL]&lt;br /&gt;
&lt;br /&gt;
{{Notes}}&lt;br /&gt;
&lt;br /&gt;
__FORCETOC__&lt;br /&gt;
&lt;br /&gt;
== Actions from Last Week ==&lt;br /&gt;
&lt;br /&gt;
* Sheila to come back on {{bug|687991}} -- crashes on alice.it without stack&lt;br /&gt;
** Fixed another bug so we could get the crash reports. Crash only showing in builds from 20110923 or earlier so appears fixed by {{bug|687768}}.&lt;br /&gt;
* Johnath to ping JB about Thunderbird participation in this meeting&lt;br /&gt;
** Sent mail, they are going to participate, but are going to lurk for a few weeks first (hi tbirders!)&lt;br /&gt;
* Johnath to ping Todd about apps participation in this meeting&lt;br /&gt;
** Sent mail...&lt;br /&gt;
&lt;br /&gt;
== Schedule &amp;amp;amp; Progress on [[Releases|Upcoming Releases]] ==&lt;br /&gt;
&lt;br /&gt;
===Firefox Desktop ===&lt;br /&gt;
==== Release (3.6, 7) ====&lt;br /&gt;
&lt;br /&gt;
==== Beta (8) ====&lt;br /&gt;
&lt;br /&gt;
==== Aurora (9) ====&lt;br /&gt;
* We got some really nice capabilities uplifted from m-c to Aurora yesterday. Here&#039;s a taste.&lt;br /&gt;
** &amp;quot;Type Inference&amp;quot; giving us up to 44% performance improvements on AWFY&lt;br /&gt;
** Twitter Search&lt;br /&gt;
** &amp;quot;Two-finger swipe for Lion&amp;quot; for back and forward navigation on Mac 10.7 Lion.&lt;br /&gt;
** &amp;quot;New Lion-ized theme for Lion&amp;quot; toolbars, icons, buttons, etc.&lt;br /&gt;
** Tweaks to the Windows theme for Win7 consistency&lt;br /&gt;
** You can now create bookmarks by dragging text URLs to bookmarks toolbar&lt;br /&gt;
** Now you can drag a link from another app and just drop it on Firefox and it will load&lt;br /&gt;
** &amp;quot;Always restore pinned tabs&amp;quot; No matter what the users settings for restoring tabs (or not) the App Tabs should always be restored.&lt;br /&gt;
** &amp;quot;Improve responsiveness of history removals&amp;quot;  deleting large numbers of history items from the Library view used to hang the browser forever. now it is much faster.&lt;br /&gt;
** &amp;quot;Add support for fave icons on jump list uri entries&amp;quot;  Windows 7 JumpLists, a pretty important windows integration feature, just got a lot better. Right click on Firefox in the taskbar and see the beautiful icon-ified jumplist popup.&lt;br /&gt;
** &amp;quot;should be able to reset a resized textarea&amp;quot;  Users can resize text areas in Firefox. If you resize a textarea and then double click on the resizer it will reset to the original dimensions. &lt;br /&gt;
** &amp;quot;Sync should never complain about a network problem anymore unless you the Sync Now menu item/toolbar button is clicked.&amp;quot; Sync is getting less noisy with its errors.&lt;br /&gt;
**  &amp;quot;Implement font-stretch property&amp;quot; was completed in 9.  It&#039;s notable because it was filed in 1999 :-)&lt;br /&gt;
** &amp;quot;add mouseenter and mouseleave DOM events&amp;quot; high-profile web devs have been begging for this for a good while.&lt;br /&gt;
** &amp;quot;Implement CSS3 columns shorthand&amp;quot; CSS 3 columns are more important than ever and with IE 10 (and Windows 9) adding support for multi-column layout, we&#039;re finally getting there with colums.&lt;br /&gt;
** &amp;quot;Implement CSS3 text-overflow: &amp;lt;left&amp;gt; &amp;lt;right&amp;gt;&amp;quot;&lt;br /&gt;
** &amp;quot;API for controlling fullscreen from content&amp;quot; (still preffed off.)&lt;br /&gt;
** &amp;quot;Implement temporal dimension portion of Media Fragments URI specification for video/audio&amp;quot; This is kind of a huge step for Open Video.&lt;br /&gt;
&lt;br /&gt;
==== Nightly (10) ====&lt;br /&gt;
* The last week of trunk development was pretty great. Most of this made the uplift to Aurora as well.&lt;br /&gt;
** Bug 635645 - consider increasing the amount of scrolling performed by using the arrow keys -- This makes us scroll fast like all the other browsers. Easy win on perceived performance.&lt;br /&gt;
** Some nice tweaks to from front-end folks&lt;br /&gt;
*** Bug 684450 - Remove stop/go/reload button affordance and streamline other location bar icons&lt;br /&gt;
*** Bug 689051 - drop the drop shadow on the back button for Windows 7&lt;br /&gt;
*** Bug 632365 - Delay status updates for links further&lt;br /&gt;
*** Bug 462117 - Add specialized video controls for small-dimension media.&lt;br /&gt;
*** Bug 472942 - VideoDocument should center video in tab&lt;br /&gt;
&lt;br /&gt;
=== Firefox Mobile  ===&lt;br /&gt;
&lt;br /&gt;
==== The bigger issues ====&lt;br /&gt;
* Will Java front-end be feasible? Doug T. is driving toward an initial pros/cons analysis over the next week&lt;br /&gt;
* Flash support will land on nightly in the next few days, need to evaluate and set criteria for whether it would be good enough to ship (Note, this is smartphones only, because it&#039;s Gingerbread and earlier, not Honeycomb)&lt;br /&gt;
* Startup shrink focus on the eng team continues and the focus is to get us ready for toronto work week. We&#039;re capturing baseline measurements for mem usage and responsiveness so that we can track optimization wins. We are also looking at analysis of metrics across release channel builds.&lt;br /&gt;
&lt;br /&gt;
==== 7 ====&lt;br /&gt;
* Released to Android market&lt;br /&gt;
* Ad-Block plus is likely the only major add-on affected by &amp;quot;hidden&amp;quot; add-on issue, no plan (let&#039;s discuss) to revert to 6.0.&lt;br /&gt;
* Reminder: Key Features in this release&lt;br /&gt;
** Copy &amp;amp; Paste&lt;br /&gt;
** Added a ‘Quit’ action to the Android menu&lt;br /&gt;
** Language detection on first-run&lt;br /&gt;
** Improved image rendering on Tegra-based tablets and phones (see bug 669851)&lt;br /&gt;
** The WebSocket API is now available in Firefox for Android (see bug 537787)&lt;br /&gt;
&lt;br /&gt;
==== 8 ====&lt;br /&gt;
&lt;br /&gt;
==== 9 ====&lt;br /&gt;
&lt;br /&gt;
* Major tablet UX refresh&lt;br /&gt;
* Webapps support&lt;br /&gt;
* More locale picker work&lt;br /&gt;
* Camera &lt;br /&gt;
* Need to make decisions on:&lt;br /&gt;
** Flash on demand (front-end patch getting better)&lt;br /&gt;
** UA&lt;br /&gt;
** Featurettes, like the Clear Private Data changes (need to triage)&lt;br /&gt;
&lt;br /&gt;
===Firefox Sync===&lt;br /&gt;
* Fx7 - [[Firefox/Features/Instant_Sync|Instant Sync]] &lt;br /&gt;
* Beta (8) - [[Firefox/Features/Instant_Sync|Instant Sync]] - remaining piece&lt;br /&gt;
** Relanded Drop single DeviceInterval to 1 hour. See  {{bug|678588}} and crash bug {{bug|598774}} for more info.&lt;br /&gt;
* Firefox 10+:&lt;br /&gt;
** [[Services/Sync/Sync_Setup_Improvements_Desktop|Improving Sync Set Up]] - In development&lt;br /&gt;
** [[Services/Sync/Push_to_device|Push to Device]] - In development. You can play with an add-on [https://addons.mozilla.org/en-US/firefox/addon/send-tab-to-device/ here].&lt;br /&gt;
** [[Services/Sync/Addon_Sync|Addon Sync]] - In development.&lt;br /&gt;
&lt;br /&gt;
===[[AMO/FlightDeck/0.9.7|Add-on Builder]]===&lt;br /&gt;
&lt;br /&gt;
=== Add-on SDK ===&lt;br /&gt;
&lt;br /&gt;
Release (1.1 -&amp;gt; Firefox 7)&lt;br /&gt;
&lt;br /&gt;
* 1.0 -&amp;gt; 1.1 repack occurred Monday, September 26&lt;br /&gt;
* repack process experienced some problems; they have now been resolved&lt;br /&gt;
* repack post-mortem to take place this week or next&lt;br /&gt;
&lt;br /&gt;
Stabilization (1.2 -&amp;gt; Firefox 7, 8)&lt;br /&gt;
&lt;br /&gt;
* second test build, 1.2b2, spun yesterday, Tuesday, September 27 ([https://groups.google.com/forum/#!topic/mozilla-labs-jetpack/7ZnM34nwpJM announcement])&lt;br /&gt;
* final release on schedule for Tuesday, October 25, two weeks before Firefox 8&lt;br /&gt;
* will probably move up final release one week to Tuesday, October 18, three weeks before Firefox 8 ([https://groups.google.com/forum/#!topic/mozilla-labs-jetpack/e0RkE4zW9ew discussion])&lt;br /&gt;
&lt;br /&gt;
Development (1.3 -&amp;gt; Firefox 8, 9)&lt;br /&gt;
&lt;br /&gt;
* merge to stabilization branch on schedule for Tuesday, October 25&lt;br /&gt;
* will probably move up merge and final release one week to ship three weeks before Firefox 9&lt;br /&gt;
&lt;br /&gt;
== Feedback Summary  ==&lt;br /&gt;
=== Desktop ===&lt;br /&gt;
Got a little busy with 7.0.1 so here&#039;s a copy-paste of the note I sent to rrrt last night:&lt;br /&gt;
&lt;br /&gt;
*Broken extensions:&lt;br /&gt;
**Yahoo Toolbar is a big one, apparently bookmarks stored there are wiped out entirely. Lots of complaints of dataloss here. (May also be bug 680802)&lt;br /&gt;
**One or two people saying noscript went missing (that&#039;s bug 680802).&lt;br /&gt;
**Lots of complaints about Norton toolbar -- [http://community.norton.com/t5/Norton-Internet-Security-Norton/Firefox-7-0-Compatibility-Patch-is-now-available/td-p/547384 Users have to update via Norton first before updating Firefox.]&lt;br /&gt;
**Kaspersky doesn&#039;t work at all.&lt;br /&gt;
**Java console also making a reappearance.&lt;br /&gt;
**1Password - From kev &amp;quot;1Password switched to a full JS implementation a while back. Users have been reluctant (from what I understand) to upgrade because there&#039;s some functionality loss.&amp;quot;&lt;br /&gt;
**Some banking extension (maybe trusteer)&lt;br /&gt;
**Roboform (also lots of complaints)&lt;br /&gt;
*Spike in people saying they lost bookmarks/favorites -- may be Yahoo toolbar. I know people about two weeks ago were saying that we &amp;quot;forced Yahoo on them&amp;quot; so I&#039;m not sure what&#039;s going on and Yahoo may have eaten the bookmarks. Or it can be the usual upgrade = profile loss.&lt;br /&gt;
*Firefox not responding randomly. (May be bug 686025 but triggered by the update or some users are saying that they are updating directly from 5 because of this problem but it&#039;s back.)&lt;br /&gt;
*Lost sessions (but we see this with almost every update) -- may be worse this time but hard to say.&lt;br /&gt;
*A few complaints about the missing http (not a lot... but some comments that it broke intranet pages and general whining)&lt;br /&gt;
*Maybe something about Yahoo mail layouts being screwed up (can&#039;t reproduce here.)&lt;br /&gt;
&lt;br /&gt;
=== Mobile ===&lt;br /&gt;
&lt;br /&gt;
== UX &amp;amp; User Research ==&lt;br /&gt;
&lt;br /&gt;
Tablet UI exploration (aka usability testing) to take place in Toronto during mobile work week (most likely Oct 18-19th). User research (aka Mary T) is looking for a developer or two to sit in on these sessions.&lt;br /&gt;
&lt;br /&gt;
== &#039;&#039;&#039;Market Insights&#039;&#039;&#039;  ==&lt;br /&gt;
&lt;br /&gt;
A [http://src.chromium.org/viewvc/chrome?view=rev&amp;amp;revision=102140 fix landed] in Chromium to synchronise extension settings.&lt;br /&gt;
&lt;br /&gt;
Amazon announced the Silk Browser for the new [http://www.youtube.com/watch?v=_u7F_56WhHk Kindle Fire] tablet.&lt;br /&gt;
&lt;br /&gt;
Rockmelt announced that they will support [http://blog.rockmelt.com/post/10524740964/coming-soon-rockmelt-beta-4-brings-the-ultimate-reading Facebook OpenGraph] in the Beta product in a few weeks.&lt;br /&gt;
&lt;br /&gt;
== Marketing, Press &amp;amp;amp; Public Reaction  ==&lt;br /&gt;
&lt;br /&gt;
== Questions, Comments, FYI ==&lt;br /&gt;
&lt;br /&gt;
== Actions this week ==&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351945</id>
		<title>Platform/2011-09-27</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351945"/>
		<updated>2011-09-27T16:41:20Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Mobile Perf Program */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
== Automation ==&lt;br /&gt;
* {{bug|688762}} - fix return codes for remote harnesses, this should reduce hanging tegras&lt;br /&gt;
* {{bug|687974}} - adb support for talos&lt;br /&gt;
* {{bug|688604}} - make talos-remote, coming soon!&lt;br /&gt;
&lt;br /&gt;
== Mobile Perf Program ==&lt;br /&gt;
* Can Joel or Clint talk to: {{bug|685632}} - Please collect RSS (memory) data during Talos testing on Android&lt;br /&gt;
* Also digging into helping Joel prioritize &amp;amp; drive which automated tests need to be fixed and helping with getting the hw lab scalable.&lt;br /&gt;
* The focus this week is to create a perf metrics matrix so we can obtain baseline measurements. This is a grassroots effort so that we can create a snapshot of the areas we need to focus on optimizing on mozilla-central in time for the mobile work week. We are focusing on &amp;quot;Macro&amp;quot; or observed measurements and will likely use a 7D/HDMI camera to capture screens&lt;br /&gt;
* Still need to land on what the spectrum of reference HW; targeting by the end of the week&lt;br /&gt;
* A draft of the matrix which will be ready for circulation tomorrow (wed).&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
&lt;br /&gt;
= Roundtable  =&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351935</id>
		<title>Platform/2011-09-27</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351935"/>
		<updated>2011-09-27T16:36:35Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Mobile Perf Program */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
== Automation ==&lt;br /&gt;
* {{bug|688762}} - fix return codes for remote harnesses, this should reduce hanging tegras&lt;br /&gt;
* {{bug|687974}} - adb support for talos&lt;br /&gt;
* {{bug|688604}} - make talos-remote, coming soon!&lt;br /&gt;
&lt;br /&gt;
== Mobile Perf Program ==&lt;br /&gt;
* Can Joel or Clint talk to: {{bug|685632}} - Please collect RSS (memory) data during Talos testing on Android&lt;br /&gt;
* The focus this week is to create a perf metrics matrix so we can obtain baseline measurements. This is a grassroots effort so that we can create a snapshot of the areas we need to focus on optimizing on mozilla-central in time for the mobile work week. We are focusing on &amp;quot;Macro&amp;quot; or observed measurements and will likely use a 7D/HDMI camera to capture screens&lt;br /&gt;
* Still need to land on what the spectrum of reference HW will be (omap 4, exynos 4210, qualcomm, &amp;amp; tegra3)&lt;br /&gt;
* A draft of the matrix which will be ready for circulation tomorrow (wed).&lt;br /&gt;
* Also digging into helping Joel prioritize &amp;amp; drive which automated tests need to be fixed and helping with getting the hw lab scalable.&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
&lt;br /&gt;
= Roundtable  =&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351934</id>
		<title>Platform/2011-09-27</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351934"/>
		<updated>2011-09-27T16:36:13Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Automation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
== Automation ==&lt;br /&gt;
* {{bug|688762}} - fix return codes for remote harnesses, this should reduce hanging tegras&lt;br /&gt;
* {{bug|687974}} - adb support for talos&lt;br /&gt;
* {{bug|688604}} - make talos-remote, coming soon!&lt;br /&gt;
&lt;br /&gt;
== Mobile Perf Program ==&lt;br /&gt;
* Can Joel or Clint talk to: {{bug|685632}} - Please collect RSS (memory) data during Talos testing on Android&lt;br /&gt;
(modifying page loader, is this two weeks out?)&lt;br /&gt;
* The focus this week is to create a perf metrics matrix so we can obtain baseline measurements. This is a grassroots effort so that we can create a snapshot of the areas we need to focus on optimizing on mozilla-central in time for the mobile work week. We are focusing on &amp;quot;Macro&amp;quot; or observed measurements and will likely use a 7D/HDMI camera to capture screens&lt;br /&gt;
* Still need to land on what the spectrum of reference HW will be (omap 4, exynos 4210, qualcomm, &amp;amp; tegra3)&lt;br /&gt;
* A draft of the matrix which will be ready for circulation tomorrow (wed).&lt;br /&gt;
* Also digging into helping Joel prioritize &amp;amp; drive which automated tests need to be fixed and helping with getting the hw lab scalable.&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
&lt;br /&gt;
= Roundtable  =&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351929</id>
		<title>Platform/2011-09-27</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351929"/>
		<updated>2011-09-27T16:33:28Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Mobile Perf Program */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
== Automation ==&lt;br /&gt;
* {{bug|688762}} - fix return codes for remote harnesses, this should reduce hanging tegras&lt;br /&gt;
* {{bug|687974}} - adb support for talos&lt;br /&gt;
* {{bug|688604}} - make talos-remote, coming soon!&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
&lt;br /&gt;
= Roundtable  =&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351622</id>
		<title>Platform/2011-09-27</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-27&amp;diff=351622"/>
		<updated>2011-09-27T03:35:14Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Mobile */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
== Mobile Perf Program ==&lt;br /&gt;
* The focus this week is to create a perf metrics matrix so we can obtain baseline measurements. This is a grassroots effort so that we can create a snapshot of the areas we need to focus on optimizing on mozilla-central in time for the mobile work week. We are focusing on &amp;quot;Macro&amp;quot; or observed measurements and will likely use a 7D/HDMI camera to capture screens&lt;br /&gt;
* Still need to land on what the spectrum of reference HW will be (omap 4, exynos 4210, qualcomm, &amp;amp; tegra3)&lt;br /&gt;
* A draft of the matrix which will be ready for circulation tomorrow (wed).&lt;br /&gt;
* Also digging into helping Joel prioritize &amp;amp; drive which automated tests need to be fixed and helping with getting the hw lab scalable.&lt;br /&gt;
&lt;br /&gt;
== Automation ==&lt;br /&gt;
* {{bug|688762}} - fix return codes for remote harnesses, this should reduce hanging tegras&lt;br /&gt;
* {{bug|687974}} - adb support for talos&lt;br /&gt;
* {{bug|688604}} - make talos-remote, coming soon!&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
&lt;br /&gt;
= Roundtable  =&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347122</id>
		<title>Platform/2011-09-06</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347122"/>
		<updated>2011-09-06T18:48:39Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Mobile Discussion  =&lt;br /&gt;
&lt;br /&gt;
Performance Program Wiki: Please visit and dive in with comments.&lt;br /&gt;
&lt;br /&gt;
https://wiki.mozilla.org/Features/MobilePerformance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Thomas: Call to action:&amp;amp;nbsp;startup shrink and memshrink are two efforts happening today. We are creating more of a program to help drive current and future performance effort to make Fx on Android lightening fast.&lt;br /&gt;
&lt;br /&gt;
*Michelle:&amp;amp;nbsp;Performance is the #1 issue for users. More people are complaining about it than flash support&lt;br /&gt;
&lt;br /&gt;
*&amp;amp;nbsp;Erin: Timeline. We need to be remarkably faster in 6 months.&lt;br /&gt;
&lt;br /&gt;
*Startup time is the first priority&lt;br /&gt;
&lt;br /&gt;
*Acctionable Bugs&amp;amp;nbsp;Can be found [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field here.]&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
* 3.6.22 and 6.0.2 (desktop and mobile) just [https://developer.mozilla.org/devnews/index.php/2011/09/06/firefox-6-0-2-and-3-6-22-security-updates-now-available/ went live]&lt;br /&gt;
* 7.0b4 will come out later today with the same fixes&lt;br /&gt;
* &#039;&#039;&#039;If you are on the book for 3.6.23 patches (the update that will ship with Firefox 7), please land them on releases/mozilla-1.9.2 ASAP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
* Tim Taubert refactored Panorama&#039;s WebProgressListener to support e10s, and to improve private browsing support WRT saving tab thumbnails ({{bug|674926}})&lt;br /&gt;
* Kev Needham worked with Twitter to add Twitter search to the Firefox search bar ({{bug|671307}})&lt;br /&gt;
* Michael Ventnor is making progress cleaning up and refactoring some autocomplete APIs to properly support inline autocomplete ({{bug|566489}})&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
* We&#039;re trying to collect code editor feedback ([http://blog.mozilla.com/devtools/2011/09/06/do-you-write-right-to-left-help-us-test-the-code-editor/ blog post])&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
* &#039;font-stretch&#039; implemented (jfkthame/jdaggett) --- 4-digit bug fixed!&lt;br /&gt;
&lt;br /&gt;
* Team status:&lt;br /&gt;
**  dbaron: reviews, investigating mobile text resizing&lt;br /&gt;
**  dholbert: CSS3 flexbox&lt;br /&gt;
**  matspal, tnikkel: bug fixing&lt;br /&gt;
**  fantasai: getting started on page-break-*&lt;br /&gt;
**  jfkthame: bug fixing, patches for Graphite font support&lt;br /&gt;
**  jwatt: converting SVG code to use display lists and be more like other layout code&lt;br /&gt;
**  heycam: WebIDL, reworking SVG text to use CSS layout&lt;br /&gt;
**  smontagu: implementing dir=&amp;quot;auto&amp;quot; and unicode-bidi:isolate/plaintext&lt;br /&gt;
**  mattwoodrow: further 3D-transforms improvements (layer sorting)&lt;br /&gt;
**  jwir3: finishing animated gif performance issue, getting started on css3 multi-column spec validation&lt;br /&gt;
&lt;br /&gt;
* Zzzzz&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
* Basic fullscreen API landed (preffed off) (cpearce)&lt;br /&gt;
** cpearce now working on UI changes needed to get it enabled by default&lt;br /&gt;
* Team status:&lt;br /&gt;
**  doublec: bug fixing&lt;br /&gt;
**  kinetik: tidying up libcubeb sound library for review&lt;br /&gt;
**  karl: reviews, tuning the lighting in the Auckland office&lt;br /&gt;
**  cpearce: fixing remaining issues with fullscreen API (such as multiprocess support)&lt;br /&gt;
**  rgiles: starting on WebVTT subtitles&lt;br /&gt;
**  derf, jmvalin: Opus work, WebRTC standards discussion, WebRTC demo hacking&lt;br /&gt;
**  rjesup: WebRTC&lt;br /&gt;
**  roc: MediaStreams processing infrastructure&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
* Rafael and Andrew found and fixed {{bug|673017}} which explains some of the mysterious cycle collector related crashes&lt;br /&gt;
* peterv found the reason for an intermittent crash seen mostly in our test automation, which is a threading issue relating to cycle collected objects (XPCWrappedJS) being reference counted off the main thread and causing intermittent crashes.&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
* USB enumeration working on windows.&lt;br /&gt;
* Progress on WebSMS. Close to having full functionality.&lt;br /&gt;
* Team Status:&lt;br /&gt;
** Kevin: WebUSB&lt;br /&gt;
** Mounir: WebSMS&lt;br /&gt;
** Bent: WebTelephony, building B2G on windows&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
* Booting up our mobile text to speech solution! Eitan Isaacson (IRC: eeejay) has joined the a11y team -- will note his arrival at next Monday&#039;s meeting. He is in data-collecting-tinker-hacking mode for this week.&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
* Check out the awesome build time charts created by Will as part of the Build Faster project: http://brasstacks.mozilla.com/gofaster&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
&#039;&#039;&#039;2011.09.06&#039;&#039;&#039;&lt;br /&gt;
* Stub Installer &#039;&#039;being rescheduled due to reviewee not showing&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Tue. 6-Sept 10:00 AM PDT&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.07&#039;&#039;&#039;&lt;br /&gt;
* Thunderbird Open Search - https://wiki.mozilla.org/Privacy/Reviews/OpenSearch&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Wed. 07-Sept, 13:00:00 PM PDT (16:00 EDT)&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.08&#039;&#039;&#039;&lt;br /&gt;
* Safebrowsing Back-end - https://wiki.mozilla.org/Fennec/Features/safebrowsing &#039;&#039;possibly being rescheduled due to reviewee conflicts&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Thur. 8, Sept, 10:00AM PDT&lt;br /&gt;
* 3P - PBJ&lt;br /&gt;
&lt;br /&gt;
Other details:&lt;br /&gt;
* IRC Channel: #security&lt;br /&gt;
* Etherpad: http://etherpad.mozilla.com:9000/secreview&lt;br /&gt;
* Dial-in Info:&lt;br /&gt;
** In office or soft phone: extension 92&lt;br /&gt;
** US/INTL: 650-903-0800 or 650-215-1282 then extension 92&lt;br /&gt;
** Toronto: 416-848-3114 then extension 92&lt;br /&gt;
** Toll-free: 800-707-2533 then password 369&lt;br /&gt;
** Conference num 624&lt;br /&gt;
&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Friday metrics outage==&lt;br /&gt;
* Data center outage for metrics&lt;br /&gt;
* ADUs are missing for Friday - everything is 0.&lt;br /&gt;
* ADUs should have been backfilled but not appearing in Socorro.&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
* Trunk stability calmed down a bit. Still seeing a number of signatures in older builds.&lt;br /&gt;
* Type Inference checkins&lt;br /&gt;
** http://bit.ly/nyYbmc&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=684797 Bug 684797] - top crash on the trunk over the weekend but looks like a fix is pending.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=676023 Bug 676023] - duped to another bug - trying to figure out if it&#039;s fixed.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683967 Bug 683967] &lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683753 Bug 683753] - top crash on mac and linux for desktop, high on the list for windows (this one is fixed but still appearing in old builds).&lt;br /&gt;
* Other - A couple of big issues related to dlls/extensions&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=684748 Bug 684748] - dll comcash installs - high on release crashes (9k+ a day crashes).&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=665775 Bug 655775] - DataMgr.dll&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
* Naoki&#039;s detailed mobile crash report - https://wiki.mozilla.org/QA/Fennec/crash_rep_05Sept2011&lt;br /&gt;
** Request to push to aurora and beta : {{bug|684599}} - crash nsDeviceMotion::DeviceMotionChanged &lt;br /&gt;
* Top Fennec crashes that need to be looked at&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=683133 Bug 683133] - reproducible regression&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=663494 Bug 663494]&lt;br /&gt;
* Issues in Core but high for Mobile&lt;br /&gt;
** http://bit.ly/nzxDv9&lt;br /&gt;
&lt;br /&gt;
= Roundtable =&lt;br /&gt;
&lt;br /&gt;
* The discussion about web app shells and profiles petered out without a decision by the webapp guys: I (bsmedberg) was under the impression that this was an urgent project. If so, can we get decisions to proceed with implementation?&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347121</id>
		<title>Platform/2011-09-06</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347121"/>
		<updated>2011-09-06T18:46:09Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Mobile Discussion  =&lt;br /&gt;
&lt;br /&gt;
https://wiki.mozilla.org/Features/MobilePerformance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Thomas: Call to action:&amp;amp;nbsp;startup shrink and memshrink are two efforts happening today. We are creating more of a program to help drive current and future performance effort to make Fx on Android lightening fast.&lt;br /&gt;
&lt;br /&gt;
*Michelle:&amp;amp;nbsp;Performance is the #1 issue for users. More people are complaining about it than flash support&lt;br /&gt;
&lt;br /&gt;
*&amp;amp;nbsp;Erin: Timeline. We need to be remarkably faster in 6 months.&lt;br /&gt;
&lt;br /&gt;
*Startup time is the first priority&lt;br /&gt;
&lt;br /&gt;
*Acctionable Bugs&amp;amp;nbsp;Can be found [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field here.]&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
* 3.6.22 and 6.0.2 (desktop and mobile) just [https://developer.mozilla.org/devnews/index.php/2011/09/06/firefox-6-0-2-and-3-6-22-security-updates-now-available/ went live]&lt;br /&gt;
* 7.0b4 will come out later today with the same fixes&lt;br /&gt;
* &#039;&#039;&#039;If you are on the book for 3.6.23 patches (the update that will ship with Firefox 7), please land them on releases/mozilla-1.9.2 ASAP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
* Tim Taubert refactored Panorama&#039;s WebProgressListener to support e10s, and to improve private browsing support WRT saving tab thumbnails ({{bug|674926}})&lt;br /&gt;
* Kev Needham worked with Twitter to add Twitter search to the Firefox search bar ({{bug|671307}})&lt;br /&gt;
* Michael Ventnor is making progress cleaning up and refactoring some autocomplete APIs to properly support inline autocomplete ({{bug|566489}})&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
* We&#039;re trying to collect code editor feedback ([http://blog.mozilla.com/devtools/2011/09/06/do-you-write-right-to-left-help-us-test-the-code-editor/ blog post])&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
* &#039;font-stretch&#039; implemented (jfkthame/jdaggett) --- 4-digit bug fixed!&lt;br /&gt;
&lt;br /&gt;
* Team status:&lt;br /&gt;
**  dbaron: reviews, investigating mobile text resizing&lt;br /&gt;
**  dholbert: CSS3 flexbox&lt;br /&gt;
**  matspal, tnikkel: bug fixing&lt;br /&gt;
**  fantasai: getting started on page-break-*&lt;br /&gt;
**  jfkthame: bug fixing, patches for Graphite font support&lt;br /&gt;
**  jwatt: converting SVG code to use display lists and be more like other layout code&lt;br /&gt;
**  heycam: WebIDL, reworking SVG text to use CSS layout&lt;br /&gt;
**  smontagu: implementing dir=&amp;quot;auto&amp;quot; and unicode-bidi:isolate/plaintext&lt;br /&gt;
**  mattwoodrow: further 3D-transforms improvements (layer sorting)&lt;br /&gt;
**  jwir3: finishing animated gif performance issue, getting started on css3 multi-column spec validation&lt;br /&gt;
&lt;br /&gt;
* Zzzzz&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
* Basic fullscreen API landed (preffed off) (cpearce)&lt;br /&gt;
** cpearce now working on UI changes needed to get it enabled by default&lt;br /&gt;
* Team status:&lt;br /&gt;
**  doublec: bug fixing&lt;br /&gt;
**  kinetik: tidying up libcubeb sound library for review&lt;br /&gt;
**  karl: reviews, tuning the lighting in the Auckland office&lt;br /&gt;
**  cpearce: fixing remaining issues with fullscreen API (such as multiprocess support)&lt;br /&gt;
**  rgiles: starting on WebVTT subtitles&lt;br /&gt;
**  derf, jmvalin: Opus work, WebRTC standards discussion, WebRTC demo hacking&lt;br /&gt;
**  rjesup: WebRTC&lt;br /&gt;
**  roc: MediaStreams processing infrastructure&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
* Rafael and Andrew found and fixed {{bug|673017}} which explains some of the mysterious cycle collector related crashes&lt;br /&gt;
* peterv found the reason for an intermittent crash seen mostly in our test automation, which is a threading issue relating to cycle collected objects (XPCWrappedJS) being reference counted off the main thread and causing intermittent crashes.&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
* USB enumeration working on windows.&lt;br /&gt;
* Progress on WebSMS. Close to having full functionality.&lt;br /&gt;
* Team Status:&lt;br /&gt;
** Kevin: WebUSB&lt;br /&gt;
** Mounir: WebSMS&lt;br /&gt;
** Bent: WebTelephony, building B2G on windows&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
* Booting up our mobile text to speech solution! Eitan Isaacson (IRC: eeejay) has joined the a11y team -- will note his arrival at next Monday&#039;s meeting. He is in data-collecting-tinker-hacking mode for this week.&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
* Check out the awesome build time charts created by Will as part of the Build Faster project: http://brasstacks.mozilla.com/gofaster&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
&#039;&#039;&#039;2011.09.06&#039;&#039;&#039;&lt;br /&gt;
* Stub Installer &#039;&#039;being rescheduled due to reviewee not showing&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Tue. 6-Sept 10:00 AM PDT&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.07&#039;&#039;&#039;&lt;br /&gt;
* Thunderbird Open Search - https://wiki.mozilla.org/Privacy/Reviews/OpenSearch&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Wed. 07-Sept, 13:00:00 PM PDT (16:00 EDT)&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.08&#039;&#039;&#039;&lt;br /&gt;
* Safebrowsing Back-end - https://wiki.mozilla.org/Fennec/Features/safebrowsing &#039;&#039;possibly being rescheduled due to reviewee conflicts&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Thur. 8, Sept, 10:00AM PDT&lt;br /&gt;
* 3P - PBJ&lt;br /&gt;
&lt;br /&gt;
Other details:&lt;br /&gt;
* IRC Channel: #security&lt;br /&gt;
* Etherpad: http://etherpad.mozilla.com:9000/secreview&lt;br /&gt;
* Dial-in Info:&lt;br /&gt;
** In office or soft phone: extension 92&lt;br /&gt;
** US/INTL: 650-903-0800 or 650-215-1282 then extension 92&lt;br /&gt;
** Toronto: 416-848-3114 then extension 92&lt;br /&gt;
** Toll-free: 800-707-2533 then password 369&lt;br /&gt;
** Conference num 624&lt;br /&gt;
&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Friday metrics outage==&lt;br /&gt;
* Data center outage for metrics&lt;br /&gt;
* ADUs are missing for Friday - everything is 0.&lt;br /&gt;
* ADUs should have been backfilled but not appearing in Socorro.&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
* Trunk stability calmed down a bit. Still seeing a number of signatures in older builds.&lt;br /&gt;
* Type Inference checkins&lt;br /&gt;
** http://bit.ly/nyYbmc&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=684797 Bug 684797] - top crash on the trunk over the weekend but looks like a fix is pending.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=676023 Bug 676023] - duped to another bug - trying to figure out if it&#039;s fixed.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683967 Bug 683967] &lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683753 Bug 683753] - top crash on mac and linux for desktop, high on the list for windows (this one is fixed but still appearing in old builds).&lt;br /&gt;
* Other - A couple of big issues related to dlls/extensions&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=684748 Bug 684748] - dll comcash installs - high on release crashes (9k+ a day crashes).&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=665775 Bug 655775] - DataMgr.dll&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
* Naoki&#039;s detailed mobile crash report - https://wiki.mozilla.org/QA/Fennec/crash_rep_05Sept2011&lt;br /&gt;
** Request to push to aurora and beta : {{bug|684599}} - crash nsDeviceMotion::DeviceMotionChanged &lt;br /&gt;
* Top Fennec crashes that need to be looked at&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=683133 Bug 683133] - reproducible regression&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=663494 Bug 663494]&lt;br /&gt;
* Issues in Core but high for Mobile&lt;br /&gt;
** http://bit.ly/nzxDv9&lt;br /&gt;
&lt;br /&gt;
= Roundtable =&lt;br /&gt;
&lt;br /&gt;
* The discussion about web app shells and profiles petered out without a decision by the webapp guys: I (bsmedberg) was under the impression that this was an urgent project. If so, can we get decisions to proceed with implementation?&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347120</id>
		<title>Platform/2011-09-06</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347120"/>
		<updated>2011-09-06T18:45:50Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Mobile Discussion  =&lt;br /&gt;
&lt;br /&gt;
https://wiki.mozilla.org/Features/MobilePerformance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
*Thomas: Call to action:&amp;amp;nbsp;startup shrink and memshrink are two efforts happening today. We are creating more of a program to help&lt;br /&gt;
&lt;br /&gt;
drive current and future performance effort to make Fx on Android lightening fast. &lt;br /&gt;
&lt;br /&gt;
*Michelle:&amp;amp;nbsp;Performance is the #1 issue for users. More people are complaining about it than flash support&lt;br /&gt;
&lt;br /&gt;
*&amp;amp;nbsp;Erin: Timeline. We need to be remarkably faster in 6 months.&lt;br /&gt;
&lt;br /&gt;
*Startup time is the first priority&lt;br /&gt;
&lt;br /&gt;
*Acctionable Bugs&amp;amp;nbsp;Can be found [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field here.]&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
* 3.6.22 and 6.0.2 (desktop and mobile) just [https://developer.mozilla.org/devnews/index.php/2011/09/06/firefox-6-0-2-and-3-6-22-security-updates-now-available/ went live]&lt;br /&gt;
* 7.0b4 will come out later today with the same fixes&lt;br /&gt;
* &#039;&#039;&#039;If you are on the book for 3.6.23 patches (the update that will ship with Firefox 7), please land them on releases/mozilla-1.9.2 ASAP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
* Tim Taubert refactored Panorama&#039;s WebProgressListener to support e10s, and to improve private browsing support WRT saving tab thumbnails ({{bug|674926}})&lt;br /&gt;
* Kev Needham worked with Twitter to add Twitter search to the Firefox search bar ({{bug|671307}})&lt;br /&gt;
* Michael Ventnor is making progress cleaning up and refactoring some autocomplete APIs to properly support inline autocomplete ({{bug|566489}})&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
* We&#039;re trying to collect code editor feedback ([http://blog.mozilla.com/devtools/2011/09/06/do-you-write-right-to-left-help-us-test-the-code-editor/ blog post])&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
* &#039;font-stretch&#039; implemented (jfkthame/jdaggett) --- 4-digit bug fixed!&lt;br /&gt;
&lt;br /&gt;
* Team status:&lt;br /&gt;
**  dbaron: reviews, investigating mobile text resizing&lt;br /&gt;
**  dholbert: CSS3 flexbox&lt;br /&gt;
**  matspal, tnikkel: bug fixing&lt;br /&gt;
**  fantasai: getting started on page-break-*&lt;br /&gt;
**  jfkthame: bug fixing, patches for Graphite font support&lt;br /&gt;
**  jwatt: converting SVG code to use display lists and be more like other layout code&lt;br /&gt;
**  heycam: WebIDL, reworking SVG text to use CSS layout&lt;br /&gt;
**  smontagu: implementing dir=&amp;quot;auto&amp;quot; and unicode-bidi:isolate/plaintext&lt;br /&gt;
**  mattwoodrow: further 3D-transforms improvements (layer sorting)&lt;br /&gt;
**  jwir3: finishing animated gif performance issue, getting started on css3 multi-column spec validation&lt;br /&gt;
&lt;br /&gt;
* Zzzzz&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
* Basic fullscreen API landed (preffed off) (cpearce)&lt;br /&gt;
** cpearce now working on UI changes needed to get it enabled by default&lt;br /&gt;
* Team status:&lt;br /&gt;
**  doublec: bug fixing&lt;br /&gt;
**  kinetik: tidying up libcubeb sound library for review&lt;br /&gt;
**  karl: reviews, tuning the lighting in the Auckland office&lt;br /&gt;
**  cpearce: fixing remaining issues with fullscreen API (such as multiprocess support)&lt;br /&gt;
**  rgiles: starting on WebVTT subtitles&lt;br /&gt;
**  derf, jmvalin: Opus work, WebRTC standards discussion, WebRTC demo hacking&lt;br /&gt;
**  rjesup: WebRTC&lt;br /&gt;
**  roc: MediaStreams processing infrastructure&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
* Rafael and Andrew found and fixed {{bug|673017}} which explains some of the mysterious cycle collector related crashes&lt;br /&gt;
* peterv found the reason for an intermittent crash seen mostly in our test automation, which is a threading issue relating to cycle collected objects (XPCWrappedJS) being reference counted off the main thread and causing intermittent crashes.&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
* USB enumeration working on windows.&lt;br /&gt;
* Progress on WebSMS. Close to having full functionality.&lt;br /&gt;
* Team Status:&lt;br /&gt;
** Kevin: WebUSB&lt;br /&gt;
** Mounir: WebSMS&lt;br /&gt;
** Bent: WebTelephony, building B2G on windows&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
* Booting up our mobile text to speech solution! Eitan Isaacson (IRC: eeejay) has joined the a11y team -- will note his arrival at next Monday&#039;s meeting. He is in data-collecting-tinker-hacking mode for this week.&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
* Check out the awesome build time charts created by Will as part of the Build Faster project: http://brasstacks.mozilla.com/gofaster&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
&#039;&#039;&#039;2011.09.06&#039;&#039;&#039;&lt;br /&gt;
* Stub Installer &#039;&#039;being rescheduled due to reviewee not showing&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Tue. 6-Sept 10:00 AM PDT&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.07&#039;&#039;&#039;&lt;br /&gt;
* Thunderbird Open Search - https://wiki.mozilla.org/Privacy/Reviews/OpenSearch&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Wed. 07-Sept, 13:00:00 PM PDT (16:00 EDT)&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.08&#039;&#039;&#039;&lt;br /&gt;
* Safebrowsing Back-end - https://wiki.mozilla.org/Fennec/Features/safebrowsing &#039;&#039;possibly being rescheduled due to reviewee conflicts&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Thur. 8, Sept, 10:00AM PDT&lt;br /&gt;
* 3P - PBJ&lt;br /&gt;
&lt;br /&gt;
Other details:&lt;br /&gt;
* IRC Channel: #security&lt;br /&gt;
* Etherpad: http://etherpad.mozilla.com:9000/secreview&lt;br /&gt;
* Dial-in Info:&lt;br /&gt;
** In office or soft phone: extension 92&lt;br /&gt;
** US/INTL: 650-903-0800 or 650-215-1282 then extension 92&lt;br /&gt;
** Toronto: 416-848-3114 then extension 92&lt;br /&gt;
** Toll-free: 800-707-2533 then password 369&lt;br /&gt;
** Conference num 624&lt;br /&gt;
&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Friday metrics outage==&lt;br /&gt;
* Data center outage for metrics&lt;br /&gt;
* ADUs are missing for Friday - everything is 0.&lt;br /&gt;
* ADUs should have been backfilled but not appearing in Socorro.&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
* Trunk stability calmed down a bit. Still seeing a number of signatures in older builds.&lt;br /&gt;
* Type Inference checkins&lt;br /&gt;
** http://bit.ly/nyYbmc&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=684797 Bug 684797] - top crash on the trunk over the weekend but looks like a fix is pending.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=676023 Bug 676023] - duped to another bug - trying to figure out if it&#039;s fixed.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683967 Bug 683967] &lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683753 Bug 683753] - top crash on mac and linux for desktop, high on the list for windows (this one is fixed but still appearing in old builds).&lt;br /&gt;
* Other - A couple of big issues related to dlls/extensions&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=684748 Bug 684748] - dll comcash installs - high on release crashes (9k+ a day crashes).&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=665775 Bug 655775] - DataMgr.dll&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
* Naoki&#039;s detailed mobile crash report - https://wiki.mozilla.org/QA/Fennec/crash_rep_05Sept2011&lt;br /&gt;
** Request to push to aurora and beta : {{bug|684599}} - crash nsDeviceMotion::DeviceMotionChanged &lt;br /&gt;
* Top Fennec crashes that need to be looked at&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=683133 Bug 683133] - reproducible regression&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=663494 Bug 663494]&lt;br /&gt;
* Issues in Core but high for Mobile&lt;br /&gt;
** http://bit.ly/nzxDv9&lt;br /&gt;
&lt;br /&gt;
= Roundtable =&lt;br /&gt;
&lt;br /&gt;
* The discussion about web app shells and profiles petered out without a decision by the webapp guys: I (bsmedberg) was under the impression that this was an urgent project. If so, can we get decisions to proceed with implementation?&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347119</id>
		<title>Platform/2011-09-06</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347119"/>
		<updated>2011-09-06T18:45:23Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Mobile Discussion  =&lt;br /&gt;
&lt;br /&gt;
https://wiki.mozilla.org/Features/MobilePerformance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Thomas: Call to action:&amp;amp;nbsp;startup shrink and memshrink are two efforts happening today. We are creating more of a program to help&lt;br /&gt;
&lt;br /&gt;
drive current and future performance effort to make Fx on Android lightening fast. &lt;br /&gt;
&lt;br /&gt;
* Michelle:&amp;amp;nbsp;Performance is the #1 issue for users. More people are complaining about it than flash support&lt;br /&gt;
&lt;br /&gt;
*&amp;amp;nbsp;Erin: Timeline. We need to be remarkably faster in 6 months. &lt;br /&gt;
&lt;br /&gt;
* Startup time is the first priority &lt;br /&gt;
&lt;br /&gt;
* Acctionable Bugs&amp;amp;nbsp;Can be found [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field here.]&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
* 3.6.22 and 6.0.2 (desktop and mobile) just [https://developer.mozilla.org/devnews/index.php/2011/09/06/firefox-6-0-2-and-3-6-22-security-updates-now-available/ went live]&lt;br /&gt;
* 7.0b4 will come out later today with the same fixes&lt;br /&gt;
* &#039;&#039;&#039;If you are on the book for 3.6.23 patches (the update that will ship with Firefox 7), please land them on releases/mozilla-1.9.2 ASAP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
* Tim Taubert refactored Panorama&#039;s WebProgressListener to support e10s, and to improve private browsing support WRT saving tab thumbnails ({{bug|674926}})&lt;br /&gt;
* Kev Needham worked with Twitter to add Twitter search to the Firefox search bar ({{bug|671307}})&lt;br /&gt;
* Michael Ventnor is making progress cleaning up and refactoring some autocomplete APIs to properly support inline autocomplete ({{bug|566489}})&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
* We&#039;re trying to collect code editor feedback ([http://blog.mozilla.com/devtools/2011/09/06/do-you-write-right-to-left-help-us-test-the-code-editor/ blog post])&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
* &#039;font-stretch&#039; implemented (jfkthame/jdaggett) --- 4-digit bug fixed!&lt;br /&gt;
&lt;br /&gt;
* Team status:&lt;br /&gt;
**  dbaron: reviews, investigating mobile text resizing&lt;br /&gt;
**  dholbert: CSS3 flexbox&lt;br /&gt;
**  matspal, tnikkel: bug fixing&lt;br /&gt;
**  fantasai: getting started on page-break-*&lt;br /&gt;
**  jfkthame: bug fixing, patches for Graphite font support&lt;br /&gt;
**  jwatt: converting SVG code to use display lists and be more like other layout code&lt;br /&gt;
**  heycam: WebIDL, reworking SVG text to use CSS layout&lt;br /&gt;
**  smontagu: implementing dir=&amp;quot;auto&amp;quot; and unicode-bidi:isolate/plaintext&lt;br /&gt;
**  mattwoodrow: further 3D-transforms improvements (layer sorting)&lt;br /&gt;
**  jwir3: finishing animated gif performance issue, getting started on css3 multi-column spec validation&lt;br /&gt;
&lt;br /&gt;
* Zzzzz&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
* Basic fullscreen API landed (preffed off) (cpearce)&lt;br /&gt;
** cpearce now working on UI changes needed to get it enabled by default&lt;br /&gt;
* Team status:&lt;br /&gt;
**  doublec: bug fixing&lt;br /&gt;
**  kinetik: tidying up libcubeb sound library for review&lt;br /&gt;
**  karl: reviews, tuning the lighting in the Auckland office&lt;br /&gt;
**  cpearce: fixing remaining issues with fullscreen API (such as multiprocess support)&lt;br /&gt;
**  rgiles: starting on WebVTT subtitles&lt;br /&gt;
**  derf, jmvalin: Opus work, WebRTC standards discussion, WebRTC demo hacking&lt;br /&gt;
**  rjesup: WebRTC&lt;br /&gt;
**  roc: MediaStreams processing infrastructure&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
* Rafael and Andrew found and fixed {{bug|673017}} which explains some of the mysterious cycle collector related crashes&lt;br /&gt;
* peterv found the reason for an intermittent crash seen mostly in our test automation, which is a threading issue relating to cycle collected objects (XPCWrappedJS) being reference counted off the main thread and causing intermittent crashes.&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
* USB enumeration working on windows.&lt;br /&gt;
* Progress on WebSMS. Close to having full functionality.&lt;br /&gt;
* Team Status:&lt;br /&gt;
** Kevin: WebUSB&lt;br /&gt;
** Mounir: WebSMS&lt;br /&gt;
** Bent: WebTelephony, building B2G on windows&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
* Booting up our mobile text to speech solution! Eitan Isaacson (IRC: eeejay) has joined the a11y team -- will note his arrival at next Monday&#039;s meeting. He is in data-collecting-tinker-hacking mode for this week.&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
* Check out the awesome build time charts created by Will as part of the Build Faster project: http://brasstacks.mozilla.com/gofaster&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
&#039;&#039;&#039;2011.09.06&#039;&#039;&#039;&lt;br /&gt;
* Stub Installer &#039;&#039;being rescheduled due to reviewee not showing&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Tue. 6-Sept 10:00 AM PDT&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.07&#039;&#039;&#039;&lt;br /&gt;
* Thunderbird Open Search - https://wiki.mozilla.org/Privacy/Reviews/OpenSearch&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Wed. 07-Sept, 13:00:00 PM PDT (16:00 EDT)&lt;br /&gt;
* 3O - ORLY&lt;br /&gt;
&#039;&#039;&#039;2011.09.08&#039;&#039;&#039;&lt;br /&gt;
* Safebrowsing Back-end - https://wiki.mozilla.org/Fennec/Features/safebrowsing &#039;&#039;possibly being rescheduled due to reviewee conflicts&#039;&#039;&lt;br /&gt;
Meeting Details:&lt;br /&gt;
* Thur. 8, Sept, 10:00AM PDT&lt;br /&gt;
* 3P - PBJ&lt;br /&gt;
&lt;br /&gt;
Other details:&lt;br /&gt;
* IRC Channel: #security&lt;br /&gt;
* Etherpad: http://etherpad.mozilla.com:9000/secreview&lt;br /&gt;
* Dial-in Info:&lt;br /&gt;
** In office or soft phone: extension 92&lt;br /&gt;
** US/INTL: 650-903-0800 or 650-215-1282 then extension 92&lt;br /&gt;
** Toronto: 416-848-3114 then extension 92&lt;br /&gt;
** Toll-free: 800-707-2533 then password 369&lt;br /&gt;
** Conference num 624&lt;br /&gt;
&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Friday metrics outage==&lt;br /&gt;
* Data center outage for metrics&lt;br /&gt;
* ADUs are missing for Friday - everything is 0.&lt;br /&gt;
* ADUs should have been backfilled but not appearing in Socorro.&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
* Trunk stability calmed down a bit. Still seeing a number of signatures in older builds.&lt;br /&gt;
* Type Inference checkins&lt;br /&gt;
** http://bit.ly/nyYbmc&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=684797 Bug 684797] - top crash on the trunk over the weekend but looks like a fix is pending.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=676023 Bug 676023] - duped to another bug - trying to figure out if it&#039;s fixed.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683967 Bug 683967] &lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683753 Bug 683753] - top crash on mac and linux for desktop, high on the list for windows (this one is fixed but still appearing in old builds).&lt;br /&gt;
* Other - A couple of big issues related to dlls/extensions&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=684748 Bug 684748] - dll comcash installs - high on release crashes (9k+ a day crashes).&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=665775 Bug 655775] - DataMgr.dll&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
* Naoki&#039;s detailed mobile crash report - https://wiki.mozilla.org/QA/Fennec/crash_rep_05Sept2011&lt;br /&gt;
** Request to push to aurora and beta : {{bug|684599}} - crash nsDeviceMotion::DeviceMotionChanged &lt;br /&gt;
* Top Fennec crashes that need to be looked at&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=683133 Bug 683133] - reproducible regression&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=663494 Bug 663494]&lt;br /&gt;
* Issues in Core but high for Mobile&lt;br /&gt;
** http://bit.ly/nzxDv9&lt;br /&gt;
&lt;br /&gt;
= Roundtable =&lt;br /&gt;
&lt;br /&gt;
* The discussion about web app shells and profiles petered out without a decision by the webapp guys: I (bsmedberg) was under the impression that this was an urgent project. If so, can we get decisions to proceed with implementation?&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347087</id>
		<title>Platform/2011-09-06</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Platform/2011-09-06&amp;diff=347087"/>
		<updated>2011-09-06T18:02:21Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- Maybe don&#039;t screw with these links unless you&#039;ve read this blog post:&lt;br /&gt;
http://blog.johnath.com/2011/01/20/automatic-date-links-in-mediawiki/&lt;br /&gt;
Just copy them to new pages and it should Just Work!&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;[[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} -1 week}}|&amp;amp;laquo; previous week]] | [[Platform|index]] | [[Platform/{{#time: Y-m-d | {{SUBPAGENAME}} +1 week}}|next week &amp;amp;raquo;]]&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Mobile Discussion  =&lt;br /&gt;
&lt;br /&gt;
https://wiki.mozilla.org/Features/MobilePerformance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Notices / Schedule =&lt;br /&gt;
* 3.6.22 and 6.0.2 (desktop and mobile) just [https://developer.mozilla.org/devnews/index.php/2011/09/06/firefox-6-0-2-and-3-6-22-security-updates-now-available/ went live]&lt;br /&gt;
* 7.0b4 will come out later today with the same fixes&lt;br /&gt;
* &#039;&#039;&#039;If you are on the book for 3.6.23 patches (the update that will ship with Firefox 7), please land them on releases/mozilla-1.9.2 ASAP&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
= Firefox Development =&lt;br /&gt;
* Tim Taubert refactored Panorama&#039;s WebProgressListener to support e10s, and to improve private browsing support WRT saving tab thumbnails ({{bug|674926}})&lt;br /&gt;
* Kev Needham worked with Twitter to add Twitter search to the Firefox search bar ({{bug|671307}})&lt;br /&gt;
* Michael Ventnor is making progress cleaning up and refactoring some autocomplete APIs to properly support inline autocomplete ({{bug|566489}})&lt;br /&gt;
&lt;br /&gt;
= Firefox Developer Tools =&lt;br /&gt;
* We&#039;re trying to collect code editor feedback ([http://blog.mozilla.com/devtools/2011/09/06/do-you-write-right-to-left-help-us-test-the-code-editor/ blog post])&lt;br /&gt;
&lt;br /&gt;
= Performance =&lt;br /&gt;
&lt;br /&gt;
= GFX =&lt;br /&gt;
&lt;br /&gt;
= JS =&lt;br /&gt;
&lt;br /&gt;
= Layout =&lt;br /&gt;
&lt;br /&gt;
* &#039;font-stretch&#039; implemented (jfkthame/jdaggett) --- 4-digit bug fixed!&lt;br /&gt;
&lt;br /&gt;
* Team status:&lt;br /&gt;
**  dbaron: reviews, investigating mobile text resizing&lt;br /&gt;
**  dholbert: CSS3 flexbox&lt;br /&gt;
**  matspal, tnikkel: bug fixing&lt;br /&gt;
**  fantasai: getting started on page-break-*&lt;br /&gt;
**  jfkthame: bug fixing, patches for Graphite font support&lt;br /&gt;
**  jwatt: converting SVG code to use display lists and be more like other layout code&lt;br /&gt;
**  heycam: WebIDL, reworking SVG text to use CSS layout&lt;br /&gt;
**  smontagu: implementing dir=&amp;quot;auto&amp;quot; and unicode-bidi:isolate/plaintext&lt;br /&gt;
**  mattwoodrow: further 3D-transforms improvements (layer sorting)&lt;br /&gt;
&lt;br /&gt;
* Zzzzz&lt;br /&gt;
&lt;br /&gt;
= Video =&lt;br /&gt;
&lt;br /&gt;
* Basic fullscreen API landed (preffed off) (cpearce)&lt;br /&gt;
** cpearce now working on UI changes needed to get it enabled by default&lt;br /&gt;
* Team status:&lt;br /&gt;
**  doublec: bug fixing&lt;br /&gt;
**  kinetik: tidying up libcubeb sound library for review&lt;br /&gt;
**  karl: reviews, tuning the lighting in the Auckland office&lt;br /&gt;
**  cpearce: fixing remaining issues with fullscreen API (such as multiprocess support)&lt;br /&gt;
**  rgiles: starting on WebVTT subtitles&lt;br /&gt;
**  derf, jmvalin: Opus work, WebRTC standards discussion, WebRTC demo hacking&lt;br /&gt;
**  rjesup: WebRTC&lt;br /&gt;
**  roc: MediaStreams processing infrastructure&lt;br /&gt;
&lt;br /&gt;
= DOM =&lt;br /&gt;
&lt;br /&gt;
= WebAPI =&lt;br /&gt;
&lt;br /&gt;
= Network =&lt;br /&gt;
&lt;br /&gt;
= Plugins =&lt;br /&gt;
&lt;br /&gt;
= Mobile =&lt;br /&gt;
&lt;br /&gt;
= Accessibility =&lt;br /&gt;
&lt;br /&gt;
= Multi-Process =&lt;br /&gt;
&lt;br /&gt;
= Tree Management =&lt;br /&gt;
&lt;br /&gt;
= Security =&lt;br /&gt;
&lt;br /&gt;
= Stability Report =&lt;br /&gt;
&lt;br /&gt;
==Friday metrics outage==&lt;br /&gt;
* Data center outage for metrics&lt;br /&gt;
* ADUs are missing for Friday - everything is 0.&lt;br /&gt;
* ADUs should have been backfilled but not appearing in Socorro.&lt;br /&gt;
&lt;br /&gt;
==Desktop==&lt;br /&gt;
* Trunk stability calmed down a bit. Still seeing a number of signatures in older builds.&lt;br /&gt;
* Type Inference checkins&lt;br /&gt;
** http://bit.ly/nyYbmc&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=684797 Bug 684797] - top crash on the trunk over the weekend but looks like a fix is pending.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=676023 Bug 676023] - duped to another bug - trying to figure out if it&#039;s fixed.&lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683967 Bug 683967] &lt;br /&gt;
* [https://bugzilla.mozilla.org/show_bug.cgi?id=683753 Bug 683753] - top crash on mac and linux for desktop, high on the list for windows (this one is fixed but still appearing in old builds).&lt;br /&gt;
* Other&lt;br /&gt;
** A couple of big issues related to dlls/extensions&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=684748 Bug 684748] - dll comcash installs - high on release crashes (9k+ a day crashes).&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=665775 Bug 655775] - DataMgr.dll&lt;br /&gt;
&lt;br /&gt;
==Mobile==&lt;br /&gt;
* Naoki&#039;s detailed mobile crash report - https://wiki.mozilla.org/QA/Fennec/crash_rep_05Sept2011&lt;br /&gt;
* Top Fennec crashes that need to be looked at&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=683133 Bug 683133] - reproducible regression&lt;br /&gt;
** [https://bugzilla.mozilla.org/show_bug.cgi?id=663494 Bug 663494]&lt;br /&gt;
* Top issues in Core but high for Mobile&lt;br /&gt;
** http://bit.ly/nzxDv9&lt;br /&gt;
&lt;br /&gt;
= Roundtable =&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347064</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347064"/>
		<updated>2011-09-06T17:46:17Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Improve startup time&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;We have measurements measurements suggesting that XUL&amp;amp;nbsp;doubles are mem usage. How can we prove/disprove that? Is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process, multithreaded architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*&lt;br /&gt;
JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;&amp;lt;br&amp;gt; &#039;&#039;&#039;Making Life&amp;amp;nbsp;Better for Users Today ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Reporting  ====&lt;br /&gt;
&lt;br /&gt;
Where are performance metrics results reported?&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://arewefastyet.com Are We Fast Yet?]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[[ https://wiki.mozilla.org/Mobile/Fennec#Performance|Fennec Performance Page]]&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Domain Experts&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Parmenter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert: Tools &amp;amp;amp; Automation Lead &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347051</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347051"/>
		<updated>2011-09-06T17:39:20Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Improve startup time&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;We have measurements measurements suggesting that XUL&amp;amp;nbsp;doubles are mem usage. How can we prove/disprove that? Is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process, multithreaded architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Reporting  ====&lt;br /&gt;
&lt;br /&gt;
Where are performance metrics results reported?&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
[http://arewefastyet.com Are We Fast Yet?]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[[ https://wiki.mozilla.org/Mobile/Fennec#Performance|Fennec Performance Page]]&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Domain Experts&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Parmenter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert: Tools &amp;amp;amp; Automation Lead &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347050</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347050"/>
		<updated>2011-09-06T17:37:56Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Improve startup time&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;We have measurements measurements suggesting that XUL&amp;amp;nbsp;doubles are mem usage. How can we prove/disprove that? Is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process, multithreaded architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Reporting ====&lt;br /&gt;
&lt;br /&gt;
[http://arewefastyet.com Are We Fast Yet?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[[ https://wiki.mozilla.org/Mobile/Fennec#Performance|Fennec Performance Page]]&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Domain Experts&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Parmenter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert: Tools &amp;amp;amp; Automation Lead &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347007</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=347007"/>
		<updated>2011-09-06T17:14:38Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Reporting ====&lt;br /&gt;
&lt;br /&gt;
[http://arewefastyet.com Are We Fast Yet?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[[ https://wiki.mozilla.org/Mobile/Fennec#Performance|Fennec Performance Page]]&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346978</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346978"/>
		<updated>2011-09-06T16:48:42Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Resources  */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Reporting ====&lt;br /&gt;
&lt;br /&gt;
[http://arewefastyet.com Are We Fast Yet?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346977</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346977"/>
		<updated>2011-09-06T16:47:36Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Current undergoing projects happening in the interest of improving performance are: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346975</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346975"/>
		<updated>2011-09-06T16:47:09Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346974</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346974"/>
		<updated>2011-09-06T16:46:30Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;Be Faster Than Native Browsers&amp;lt;br&amp;gt;Top Goals&lt;br /&gt;
&lt;br /&gt;
Understand memory usage &lt;br /&gt;
&lt;br /&gt;
Reduce memory usage in a fanatical way &lt;br /&gt;
&lt;br /&gt;
Improve Perceived Performance &lt;br /&gt;
&lt;br /&gt;
Fix Panning Performance &lt;br /&gt;
&lt;br /&gt;
Mobile is Everywhere&lt;br /&gt;
&lt;br /&gt;
A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot; &lt;br /&gt;
&lt;br /&gt;
A phone and a tablet are two entirely different instruments so are we creating three firefoxes, two firefoxes, or one firefox? &lt;br /&gt;
&lt;br /&gt;
Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot; efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation &lt;br /&gt;
&lt;br /&gt;
Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration. We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility. &lt;br /&gt;
&lt;br /&gt;
Front End&amp;lt;br&amp;gt;Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&lt;br /&gt;
&lt;br /&gt;
Identify what these changes are and what they cost &lt;br /&gt;
&lt;br /&gt;
Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction &lt;br /&gt;
&lt;br /&gt;
Non-XUL Front End Architecture? Our current measurements say that XUL doubles are mem usage- is this fixable? &lt;br /&gt;
&lt;br /&gt;
Platform &amp;amp;amp; Architecture&amp;lt;br&amp;gt;Do we want to move to a single process architecture? &amp;lt;br&amp;gt;P1&lt;br /&gt;
&lt;br /&gt;
UI responsiveness:slow, no progress bar &lt;br /&gt;
&lt;br /&gt;
Tap, Pan, Zoom:Checkerboarding &lt;br /&gt;
&lt;br /&gt;
Memory Usage:We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?) &lt;br /&gt;
&lt;br /&gt;
Footprint: Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &lt;br /&gt;
&lt;br /&gt;
Startup Speed: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare &lt;br /&gt;
&lt;br /&gt;
P2&lt;br /&gt;
&lt;br /&gt;
Page Load: Depends upon the website (and probably the kind of phone/tablet people are running). &lt;br /&gt;
&lt;br /&gt;
P3&lt;br /&gt;
&lt;br /&gt;
JavasScript: We are 2x faster than stock &lt;br /&gt;
&lt;br /&gt;
Making Life Better for Users Today &lt;br /&gt;
&lt;br /&gt;
There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &lt;br /&gt;
&lt;br /&gt;
ARMv6 phones are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior. &lt;br /&gt;
&lt;br /&gt;
Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084 &lt;br /&gt;
&lt;br /&gt;
Schedule&amp;lt;br&amp;gt;Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&lt;br /&gt;
&lt;br /&gt;
Connect: We should take September to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy. &lt;br /&gt;
&lt;br /&gt;
Pounce: Launch an acctionable project plan on or before October 3 &lt;br /&gt;
&lt;br /&gt;
Create plan for : October-March &lt;br /&gt;
&lt;br /&gt;
Actionnable Items&lt;br /&gt;
&lt;br /&gt;
Scrub this bug list and see how this maps to our goals, what the delta is, and get traction. &lt;br /&gt;
&lt;br /&gt;
Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla? &lt;br /&gt;
&lt;br /&gt;
0.5s XUL reflows&amp;lt;br&amp;gt; 0.5s sqlite IO (150-1000ms, avg 500)&amp;lt;br&amp;gt; ~0.5s linker badness (needs linker improvements)&amp;lt;br&amp;gt; unknown needlessly parsing XML, CSS, etc. &lt;br /&gt;
&lt;br /&gt;
We need tools to better understand Memory Usage on Android- teach people how to profile on Android &lt;br /&gt;
&lt;br /&gt;
We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course) &lt;br /&gt;
&lt;br /&gt;
Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
Plan of attack for all-hands; golden opportunity to spread the message &lt;br /&gt;
&lt;br /&gt;
Project plan &amp;amp;amp; schedule &lt;br /&gt;
&lt;br /&gt;
Resources&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt;Current undergoing projects happening in the interest of improving performance are:&lt;br /&gt;
&lt;br /&gt;
MemShrink&lt;br /&gt;
&lt;br /&gt;
StartupShrink&lt;br /&gt;
&lt;br /&gt;
B2G&lt;br /&gt;
&lt;br /&gt;
Pancake&lt;br /&gt;
&lt;br /&gt;
GoFaster?&lt;br /&gt;
&lt;br /&gt;
===&lt;br /&gt;
&lt;br /&gt;
Ionmonkey? &lt;br /&gt;
&lt;br /&gt;
Firestarters/Thought Leaders&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&lt;br /&gt;
&lt;br /&gt;
David Mandelin&lt;br /&gt;
&lt;br /&gt;
Mark Finkle&lt;br /&gt;
&lt;br /&gt;
DRIs&lt;br /&gt;
&lt;br /&gt;
Mark Finkle: Mobile Front-End Lead&lt;br /&gt;
&lt;br /&gt;
Stuart Perameter: Pancake Lead (this is Firefox home app?)&lt;br /&gt;
&lt;br /&gt;
Clint Talbert: Are we fast yet person&lt;br /&gt;
&lt;br /&gt;
Taras Gleck: Performance Manager&lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg&lt;br /&gt;
&lt;br /&gt;
Who else? &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346973</id>
		<title>Features/MobilePerformance</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Features/MobilePerformance&amp;diff=346973"/>
		<updated>2011-09-06T16:45:27Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: Created page with &amp;quot;test&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;test&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346961</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346961"/>
		<updated>2011-09-06T16:39:32Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039;slow, no progress bar&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Tap, Pan, Zoom:&#039;&#039;&#039;Checkerboarding&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Memory Usage:&#039;&#039;&#039;We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
*Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
*JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
*Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
*Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Create plan for&amp;amp;nbsp;:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
*[https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals&lt;br /&gt;
&lt;br /&gt;
*Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Performance/MemShrink MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/Firefox/Projects/Mobile_Startup_Shrink StartupShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[https://wiki.mozilla.org/B2G B2G]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346959</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346959"/>
		<updated>2011-09-06T16:37:18Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Current undergoing projects happening in the interest of improving performance are: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
* Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Create plan for :&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
* Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
[MemShrink][https://wiki.mozilla.org/Performance/MemShrink]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346958</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346958"/>
		<updated>2011-09-06T16:36:06Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Actionnable Items */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
* Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Create plan for :&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
* Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346957</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346957"/>
		<updated>2011-09-06T16:35:45Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Actionnable Items */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
* Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Create plan for :&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* &amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
* Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346954</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346954"/>
		<updated>2011-09-06T16:34:48Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Raising the Mainsail: take time to do it right to avoid snags but don&amp;#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
* Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Create plan for :&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346953</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346953"/>
		<updated>2011-09-06T16:34:14Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* P2 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
* Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346952</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346952"/>
		<updated>2011-09-06T16:33:53Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* P3 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346949</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346949"/>
		<updated>2011-09-06T16:33:12Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* P1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346948</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346948"/>
		<updated>2011-09-06T16:32:42Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* P1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;* UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;* Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;* Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;* Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;* Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346947</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346947"/>
		<updated>2011-09-06T16:32:08Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
* Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Architect these changes so they are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346944</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346944"/>
		<updated>2011-09-06T16:31:20Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Mobile is Everywhere */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346942</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346942"/>
		<updated>2011-09-06T16:29:20Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Top Goals  */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
* Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
* Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346938</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346938"/>
		<updated>2011-09-06T16:26:41Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* DRIs  */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ux: Alex Faaborg &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346936</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346936"/>
		<updated>2011-09-06T16:25:42Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* DRIs  */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Alex Faaborg and Alex Limi&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346242</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346242"/>
		<updated>2011-09-02T20:28:12Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Thought Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who is Ux?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346223</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346223"/>
		<updated>2011-09-02T19:55:22Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039;  =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- Understand memory usage &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Reduce memory usage in a fanatical way&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Improve Perceived Performance &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Fix Panning Performance&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture  ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P2  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt;  ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t squander the wind We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows &lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500) &lt;br /&gt;
#~0.5s linker badness (needs linker improvements) &lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt;  ==&lt;br /&gt;
&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Though Leaders&amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Asa&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt;  ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who is Ux?&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346222</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346222"/>
		<updated>2011-09-02T19:52:01Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* P1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039; =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
=== P1s&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
P2s&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t miss the wind. We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows&lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500)&lt;br /&gt;
#~0.5s linker badness (needs linker improvements)&lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt; ==&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Though Leaders&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Asa&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Who is Ux?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346221</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346221"/>
		<updated>2011-09-02T19:50:54Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: /* Firefox Mobile: Mach Go Go Go! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach GoGoGo!&amp;lt;br&amp;gt;&#039;&#039;&#039; =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
P2&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t miss the wind. We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows&lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500)&lt;br /&gt;
#~0.5s linker badness (needs linker improvements)&lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt; ==&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Though Leaders&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Asa&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Who is Ux?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346217</id>
		<title>Temp/</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=Temp/&amp;diff=346217"/>
		<updated>2011-09-02T19:39:53Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: Created page with &amp;quot;= &amp;#039;&amp;#039;&amp;#039;Firefox Mobile: Mach Go Go Go!&amp;lt;br&amp;gt;&amp;#039;&amp;#039;&amp;#039; =  == Be Faster Than Native Browsers&amp;lt;br&amp;gt; ==  == Top Goals &amp;lt;br&amp;gt; ==  - Understand memory usage &amp;lt;br&amp;gt;  - Reduce memory usage in a fanatical...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= &#039;&#039;&#039;Firefox Mobile: Mach Go Go Go!&amp;lt;br&amp;gt;&#039;&#039;&#039; =&lt;br /&gt;
&lt;br /&gt;
== Be Faster Than Native Browsers&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
== Top Goals &amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- Understand memory usage &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Reduce memory usage in a fanatical way&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Improve Perceived Performance &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Fix Panning Performance&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Mobile is Everywhere&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- A laptop is mobile but users run firefox &amp;quot;desktop&amp;quot;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- A phone and a tablet are two entirely different instruments so are we creating &#039;&#039;&#039;three firefoxes&#039;&#039;&#039;, &#039;&#039;&#039;two firefoxes&#039;&#039;&#039;, or &#039;&#039;&#039;one firefox? &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Mobile and desktop are converging. This means the people need to converge, too. We need to identify the &amp;quot;strata&amp;quot;&amp;amp;nbsp;efforts that are happening already and create visibility and summary and as far as product is concerned, they should be on autopilot so Product can focus on innovation&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Metrics and numbers are good to get people to fix bugs but they are not enough incentive to create the much needed cultural shift of collaboration and integration.&amp;amp;nbsp;We need to depict to everyone what it is that we are talking about when we say Firefox is slower than native browsers and we need to do so in a public forum. This is not about shame. This is about celebrating the world of possibility.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Front End&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
==== Perception Design: Identify ux improvements we can make that will elevate perceived performance while we work to make Firefox faster on Android&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
- Identify what these changes are and what they cost&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Architect them so these changes are scalable and fluid for users as we make progress with under the hood performance improvements. They shouldn&#039;t break as Startup Shrink and Mem Kill continue to make traction&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Non-XUL Front End Architecture?&amp;amp;nbsp;Our current measurements say that XUL&amp;amp;nbsp;doubles are mem usage- is this fixable?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Platform &amp;amp;amp; Architecture ==&lt;br /&gt;
&lt;br /&gt;
==== Do we want to move to a single process architecture?&amp;amp;nbsp;&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
=== P1&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- UI&amp;amp;nbsp;responsiveness:&#039;&#039;&#039; slow, no progress bar&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Tap, Pan, Zoom:&#039;&#039;&#039; Checkerboarding&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Memory Usage:&#039;&#039;&#039; We don&#039;t really know but we think it is badDifficult to understand in Android, we need to set goals. Use 85% less memory than Chrome by March 2012, 50% by December, 25% by October (Memshrink Project?)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Footprint:&#039;&#039;&#039;&amp;amp;nbsp;Install footprint is currently 14MB. Keep measuring this as code changes and features are added. &#039;&#039;&#039;&amp;lt;br&amp;gt;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Startup Speed&#039;&#039;&#039;: 5s stock is 1.5s Part perception, part architecture (StartupShrink?). Measure both Cold and Warm startup and compare&amp;lt;br&amp;gt;&lt;br /&gt;
P2&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- Page Load:&#039;&#039;&#039;&amp;amp;nbsp;Depends upon the website (and probably the kind of phone/tablet people are running).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== P3&amp;lt;br&amp;gt; ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;- JavasScript:&#039;&#039;&#039;&amp;amp;nbsp;We are 2x faster than stock&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Making Life&amp;amp;nbsp;Better for Users Today &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-There are some phones that will rock with Firefox and some that will not even run Firefox. We can do something about this today. Do we publish this information? &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- [http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/79077e355504098d# ARMv6 phones] are not supported and we need to map that to something purchasers of phones and users of Firefox can translate into behavior.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Stabilize: CrashKill is happening, will some of the crashes fix performance for free? Keep up on top bugs such as 475084&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Schedule&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
==== Raising the Mainsail: take time to do it right to avoid snags but don&#039;t miss the wind. We need to be in an entirely different state of affairs by March 2012. That is 6 months from now.&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Connect: We should take &#039;&#039;&#039;September &#039;&#039;&#039;to connect, aggregate, investigate, understand, and set a course. People are working on things today and we need to seek to understand what the intended results are and how they map to the larger strategy.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pounce:&amp;amp;nbsp;Launch an acctionable project plan on or before &#039;&#039;&#039;October 3 &#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TBD:&amp;amp;nbsp;&#039;&#039;&#039;October-March&#039;&#039;&#039;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Actionnable Items&amp;lt;br&amp;gt; ==&lt;br /&gt;
&lt;br /&gt;
- (Before Tuesday Meeting) [https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&amp;amp;field1-0-3=rep_platform&amp;amp;field0-0-0=keywords&amp;amp;field1-0-2=op_sys&amp;amp;value1-0-3=ARM&amp;amp;type1-0-1=equals&amp;amp;value1-0-1=Fennec&amp;amp;resolution=---&amp;amp;type1-0-2=equals&amp;amp;type1-0-3=equals&amp;amp;value1-0-2=Android&amp;amp;query_format=advanced&amp;amp;value1-0-0=mobile&amp;amp;type0-0-0=substring&amp;amp;value0-0-0=perf&amp;amp;field1-0-0=keywords&amp;amp;field1-0-1=product&amp;amp;list_id=1204614 Scrub this bug list ]and see how this maps to our goals, what the delta is, and get traction. &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Tara&#039;s ID&#039;d these items as being wasted on startup, are they being tracked in Bugzilla?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#0.5s XUL reflows&lt;br /&gt;
#0.5s sqlite IO (150-1000ms, avg 500)&lt;br /&gt;
#~0.5s linker badness (needs linker improvements)&lt;br /&gt;
#unknown needlessly parsing XML, CSS, etc.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need tools to better understand Memory Usage on Android- teach people how to profile on Android&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- We need someone to audit desktop&#039;s tools to see if they work for Fennec and if not, work on achieving parity (and innovating of course)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-&amp;amp;nbsp; Connect with Boot to Gecko and Pancake teams to understand on orwhat is happening today and evangelize the super set of performance goals &lt;br /&gt;
&lt;br /&gt;
- Plan of attack for all-hands; golden opportunity to spread the message &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
- Project plan &amp;amp;amp; schedule&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Resources &amp;lt;br&amp;gt; ==&lt;br /&gt;
IRC Channels?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
http://arewefastyet.com&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Current undergoing projects happening in the interest of improving performance are:&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
MemShrink&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
StartupShrink&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Boot to Gecko&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pancake &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/3f570f92783d8ede# GoFaster?]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ionmonkey?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Firestarters/Though Leaders&amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Thomas Arend&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Asa&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
David Mandelin&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Mark Finkle&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== DRIs &amp;lt;br&amp;gt; ====&lt;br /&gt;
&lt;br /&gt;
Mark Finkle:&amp;amp;nbsp;Mobile Front-End Lead&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Stuart Perameter:&amp;amp;nbsp;Pancake Lead (this is Firefox home app?)&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Clint Talbert:&amp;amp;nbsp;Are we fast yet person&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Taras Gleck:&amp;amp;nbsp;Performance Manager &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Who is Ux?&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Who else?&amp;amp;nbsp;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
	<entry>
		<id>https://wiki.mozilla.org/index.php?title=CrashKill&amp;diff=346139</id>
		<title>CrashKill</title>
		<link rel="alternate" type="text/html" href="https://wiki.mozilla.org/index.php?title=CrashKill&amp;diff=346139"/>
		<updated>2011-09-02T16:44:40Z</updated>

		<summary type="html">&lt;p&gt;ErinLancaster: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
==General Agenda==&lt;br /&gt;
Crashkill covers the tracking and escalation of stability issues for both Desktop and Mobile products.&lt;br /&gt;
&lt;br /&gt;
* Track general stability for all our releases and development channels.&lt;br /&gt;
* Triage Top Crashes to find owners, set priorities, and identify vender outreach issues.&lt;br /&gt;
* Identify top tools issues so we can find &amp;amp; fix faster.&lt;br /&gt;
* Identify the first thing we want to do to increase developer awareness and commitment to fixing top crashers.&lt;br /&gt;
* Identify the first thing we want to automate.&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
A list of links to reports we run frequently for monitoring stability.&lt;br /&gt;
&lt;br /&gt;
* https://crash-stats.mozilla.com/products/Firefox&lt;br /&gt;
* https://crash-stats.mozilla.com/products/Fennec&lt;br /&gt;
* https://crash-analysis.mozilla.com/chofmann/&lt;br /&gt;
* https://wiki.mozilla.org/Temp/&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
=== Desktop ===&lt;br /&gt;
* Channel stability&lt;br /&gt;
** [https://wiki.mozilla.org/CrashKill/Nightly Nightly top crashers and trends]&lt;br /&gt;
** [https://wiki.mozilla.org/CrashKill/Aurora Aurora top crashers and trends]&lt;br /&gt;
** [https://wiki.mozilla.org/CrashKill/Beta Beta top crashers and trends]&lt;br /&gt;
*  [https://wiki.mozilla.org/CrashKill/Plan Gathering and organizing engineering requirements for Socorro features and reports ]&lt;br /&gt;
* 10.7 (Lion) crashes&lt;br /&gt;
** [http://bit.ly/ny2xan Open 10.7 crashes]&lt;br /&gt;
** [http://bit.ly/oqa7WN Fixed 10.7 crashes]&lt;br /&gt;
* Flash related issues&lt;br /&gt;
** We are keeping track of Flash related hangs and crashes in [https://wiki.mozilla.org/CrashKill/Flash this wiki page]&lt;br /&gt;
* Historical stuff&lt;br /&gt;
**  [https://wiki.mozilla.org/CrashKill/Firefox4 Crash monitoring and trends for Firefox 4 release]&lt;br /&gt;
&lt;br /&gt;
===Mobile===&lt;br /&gt;
&lt;br /&gt;
* Helpful reports&lt;br /&gt;
** https://crash-analysis.mozilla.com/crash_stacks/Stack-summary-9.0a1-mobile.txt&lt;br /&gt;
** https://crash-analysis.mozilla.com/crash_stacks/Stack-summary-6.0-mobile.txt&lt;br /&gt;
** https://crash-analysis.mozilla.com/crash_stacks/Stack-summary-6.0-mobile-wo-libc.txt&lt;br /&gt;
* Trunk stability&lt;br /&gt;
** [http://bit.ly/nzxDv9 Mobile crashes in Core]&lt;br /&gt;
** [http://bit.ly/oHX0Z5 Mobile top crashes]&lt;br /&gt;
** [http://bit.ly/pW4ObW All Mobile crashes]&lt;br /&gt;
* Weekly reports&lt;br /&gt;
** [https://wiki.mozilla.org/QA/Fennec/crash_rep_29Aug2011 Crash report for Aug 29, 2011]&lt;br /&gt;
* Other stuff we are tracking&lt;br /&gt;
** Skiplist bug [https://bugzilla.mozilla.org/show_bug.cgi?id=683385 Bug 683385]&lt;br /&gt;
&lt;br /&gt;
==Meeting logistics==&lt;br /&gt;
* Monday @ 10:00am PDT&lt;br /&gt;
{{conf|290}}&lt;br /&gt;
* *1 to unmute yourself&lt;br /&gt;
* join irc.mozilla.org #crashkill for back channel&lt;br /&gt;
* Mountain View conference room &amp;quot;Zombocom&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==Meeting notes==&lt;br /&gt;
* [[CrashKill/2011-08-29|Monday, Aug 29, 10:00am PST]]&lt;br /&gt;
* [[CrashKill/2011-08-22|Monday, Aug 22, 10:00am PST]]&lt;br /&gt;
* [[CrashKill/2011-08-15|Monday, Aug 15, 10:00am PST]]&lt;br /&gt;
* [[CrashKill/2011-08-08|Monday, Aug 08, 10:00am PST]]&lt;br /&gt;
* [[CrashKill/2011-08-02|Tuesday, Aug 2, 10:00am PST]]&lt;br /&gt;
* [[CrashKill/2011-07-18|Monday, July 18, 10:00am]]&lt;br /&gt;
* [[CrashKill/2011-06-27|Monday, June 27, 10:00am]]&lt;br /&gt;
* [[CrashKill/2011-05-02|Monday, May 2, 10:30am]]&lt;br /&gt;
* [[CrashKill/2010-08-10|Tuesday, August 10, 12:30pm]]&lt;br /&gt;
* [[CrashKill/2010-05-04|Tuesday, May 4, 12:30pm]]&lt;br /&gt;
* [[CrashKill/2010-03-01|Monday, March 1, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2010-02-08|Monday, February 8, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2010-02-01|Monday, February 1, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2009-12-14|Monday, December 14, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2009-11-30|Monday, November 30, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2009-11-23|Monday, November 23, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2009-11-16|Monday, November 16, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2009-11-09|Monday, November 9, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2009-11-02|Monday, November 2, 3pm PST]]&lt;br /&gt;
* [[CrashKill/2009-10-26|Monday, October 26, 3pm PDT]]&lt;br /&gt;
* [[CrashKill/2009-10-19|Monday, October 19, 3pm PDT]]&lt;br /&gt;
* [[CrashKill/2009-10-12|Monday, October 12, 3pm PDT]]&lt;br /&gt;
* [[CrashKill/2009-10-05|Monday, October 5, 3pm PDT]]&lt;br /&gt;
* [[CrashKill/2009-09-28|Monday, September 28, 3pm PDT]]&lt;br /&gt;
&lt;br /&gt;
==Old Stuff==&lt;br /&gt;
=== Bug lists ===&lt;br /&gt;
* [http://bit.ly/3K8mhq The CrashKill Bugs]  &amp;lt;small&amp;gt;(Status Whiteboard: [crashkill])&amp;lt;/small&amp;gt;&lt;br /&gt;
* {{Crash-ThirdParty| [http://bit.ly/1TlEts CrashKill Bugs caused by third parties] }} &amp;lt;small&amp;gt;(Status Whiteboard: [crashkill-thirdparty])&amp;lt;/small&amp;gt;&lt;br /&gt;
* {{Crash-Blocklist| [http://bit.ly/33K46O Crashkill Bugs where we&#039;re considering blocking the addon/dll] }}  &amp;lt;small&amp;gt;(Status Whiteboard: [crashkill-block])&amp;lt;/small&amp;gt;&lt;br /&gt;
* {{Crash-Fixed| [http://bit.ly/2aFggC CrashKill Bugs where we&#039;ve provided a fix] of some kind, even if just a wallpaper or skidmark }}  &amp;lt;small&amp;gt;(Status Whiteboard: [crashkill-fix])&amp;lt;/small&amp;gt;&lt;br /&gt;
* {{Crash-Debug| [http://bit.ly/3qmv2U CrashKill Bugs where we&#039;ve provide a patch only to help debug the problem] }} &amp;lt;small&amp;gt;(Status Whiteboard: [crashkill-debug])&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [http://bit.ly/Uf9J5 List] of bugs tracking metrics improvements for CrashKill efforts.  &amp;lt;small&amp;gt;(Status Whiteboard: [crashkill-metrics])&amp;lt;/small&amp;gt;&lt;br /&gt;
* nominate bugs for the 3.6-only DLL blocklist by adding a dependency to {{bug|525103}}&lt;br /&gt;
* [http://bit.ly/6Cv0v7 SkipList Bugs] and [https://wiki.mozilla.org/Breakpad/SkipList how to make a SkipList] request&lt;br /&gt;
&lt;br /&gt;
=== Analysis ===&lt;br /&gt;
* [http://crash-stats.mozilla.com/topcrasher/byversion/Firefox/3.5.5/7 Firefox 3.5.5 top crashes in the last week]&lt;br /&gt;
* [http://crash-stats.mozilla.com/topcrasher/byversion/Firefox/3.6b4/7 Firefox 3.6 beta 4 top crashes in the last week]&lt;br /&gt;
* [http://people.mozilla.com/crash_analysis/ Correlation Reports]&lt;br /&gt;
* [[CrashKill/Signatures|Crash signatures by module]]&lt;br /&gt;
* [http://people.mozilla.com/~chofmann/crash-data/new-crashes/ chofmann&#039;s new crash signatures]&lt;br /&gt;
* [http://people.mozilla.org/~jst/new-crashes/Firefox/latest/ jst&#039;s new crash signatures, running daily]&lt;br /&gt;
* [http://bit.ly/4XsjUp Outreach Bugs] tracking our efforts to contact add on vendors who have products causing crashes that we want to kill.&lt;br /&gt;
* [https://wiki.mozilla.org/CrashKill/CrashDash crash bug trend dashboard]  some metrics around crash bugs filed, fixed, and resolved through triage.&lt;br /&gt;
&lt;br /&gt;
* [http://www.squarefree.com/2009/10/15/531/ How to sort a bug list in topcrash order]&lt;br /&gt;
* [[CrashKill/Mac Flash Identifiers|Mac Flash Identifiers]] - Turns &amp;quot;025105C956638D665850591768FB743D0&amp;quot; into &amp;quot;Flash 10.0.32.18 on PPC&amp;quot;&lt;/div&gt;</summary>
		<author><name>ErinLancaster</name></author>
	</entry>
</feed>