(dormant account) Reporter
	Description • 15 years ago

This is on N810, with performance cpu governor to rule out cpu scaling.

here is an example log:
loading file:///usr/local/fennec/fennec/components/BrowserStartup.js 6ms
loading file:///usr/local/fennec/fennec/xulrunner/modules/XPCOMUtils.jsm 5ms
loading file:///usr/local/fennec/fennec/xulrunner/components/nsUpdateService.js 44ms
loading file:///usr/local/fennec/fennec/xulrunner/components/nsTryToClose.js 1ms
loading file:///usr/local/fennec/fennec/xulrunner/components/nsBlocklistService.js 17ms
loading file:///usr/local/fennec/fennec/xulrunner/components/nsExtensionManager.js 99ms
loading file:///usr/local/fennec/fennec/xulrunner/components/jsconsole-clhandler.js 2ms
loading file:///usr/local/fennec/fennec/xulrunner/components/nsDefaultCLH.js 4ms
loading file:///usr/local/fennec/fennec/xulrunner/modules/SpatialNavigation.js 6ms
loading file:///usr/local/fennec/fennec/xulrunner/modules/utils.js 28ms
loading file:///usr/local/fennec/fennec/xulrunner/modules/PluralForm.jsm 5ms
loading file:///usr/local/fennec/fennec/xulrunner/modules/DownloadUtils.jsm 5ms
loading file:///usr/local/fennec/fennec/xulrunner/components/nsLoginManager.js 15ms
loading file:///usr/local/fennec/fennec/components/AboutRedirector.js 4ms

Another thing that puzzles me is that there is a great deal of variability. For example nsExtensionManager can take anywhere from 99ms to 180ms to load.

This is measuring JS_XDRScript calls: http://mxr.mozilla.org/mozilla-central/source/js/src/xpconnect/loader/mozJSComponentLoader.cpp#447

There is relatively little data being parsed. 6032,3620, 1408bytes for top 3 offenders.

	(dormant account) Reporter
	Comment 1 • 15 years ago

This isn't an issue anymore