On 01/18/2017 08:11 PM, J. Ryan Stinnett wrote:
Thanks for checking it out!
I guess the reading from / writing to disk is only for speeding up
initial load of the first window then?
reading is for speeding up the initial load, and once prototype has been
loaded, no new
loads are needed, since the prototype can be used as such to generate document
objects.
We don't have anything like that for html/xhtml documents, they are always
loaded/parsed from scratch.
But, I wonder if we could use XUL documents with xhtml content. That should
still use the prototype setup
-Olli
- Ryan
On Wed, Jan 18, 2017 at 12:50 AM, smaug <sm...@welho.com> wrote:
On 01/18/2017 08:28 AM, smaug wrote:
On 01/17/2017 10:51 PM, J. Ryan Stinnett wrote:
On Mon, Jan 16, 2017 at 3:08 PM, smaug <sm...@welho.com> wrote:
On 01/16/2017 10:43 PM, Dave Townsend wrote:
One of the things I've been investigating since moving back to the
desktop
team is how we can remove XUL from the application as much as possible.
The
benefits for doing this are varied, some obvious examples:
* XUL is a proprietary standard and we barely maintain it.
* Shallower learning curve for new contributors who may already know
and
use HTML.
* HTML rendering is more optimized in the platform than XUL.
But XUL has prototype cache which makes for parsing faster and opening
new
windows even faster
since one needs to just clone from the prototype, and not load anything.
So, be careful with the performance numbers.
I am not very familiar with the details of XUL prototype cache, but my
understanding of bug 1286082[1] is that currently the XUL prototype
cache is not actually working correctly (and possibly has been broken
since bug 592943[2] landed as part of Firefox 7 in 2011).
So, an even more careful investigation / comparison is warranted. The
prototype cache might not currently be doing anything.
[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1286082
[2]: https://bugzilla.mozilla.org/show_bug.cgi?id=592943
- Ryan
those looks like about reading/writing to disk, not about the cache
itself, which should still help quite a bit with new window performance.
We did get significant performance regression when starting to use html
for...hm, was it about:newtab or about:home or what.
And https://bugzilla.mozilla.org/show_bug.cgi?id=1286082 is only about
some case, not all, as far as I see, but let me test.
Just tested and we seem to load for example
chrome://browser/content/browser.xul
chrome://global/content/editMenuOverlay.xul
chrome://browser/content/baseMenuOverlay.xul
chrome://browser/content/places/placesOverlay.xul
loaded chrome://layoutdebug/content/layoutdebug-overlay.xul
chrome://browser/content/report-phishing-overlay.xul
successfully when starting browser.
And once those are loaded, they don't need to be loaded again when opening
new windows.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
