On 04/22/2013 12:12 PM, Jeff Muizelaar wrote: > On 2013-04-22, at 2:15 PM, Bill McCloskey wrote: > >> I can't agree with you more, Justin. I think Boris is right that we should >> make these decisions on a case-by-case basis. But in the case of these >> workers, it seems clear that converting them to C++ is the way to go, >> assuming we have the resources to do so. > So a specific case that I ran into during the Performance Workshop is > RILContentHelper.js. During the startup of the settings app > we jank for 53ms while initializing the RILContentHelper.js: > > http://people.mozilla.com/~bgirard/cleopatra/#report=bf7077c6552fe2bc015d7074a338b673911f3ce8&search=Mobile
That link gives me this: "Error fetching profile :(. URL: 'http://profile-store.commondatastorage.googleapis.com/bf7077c6552fe2bc015d7074a338b673911f3ce8'. Did you set the CORS headers?" > > There doesn't seem to be anything specific taking that much time in the > profile, just general JS overhead. In this case RILContentHelper.js is > wrapped by by C++ code in dom/network/src/MobileConnection.cpp and so we end > up spending a fair amount of time transitioning from JS to C++ to JS to C++. That seems like the sort of thing that SpiderMonkey may be able to address in the short term, depending on what exactly it turns out to be. Is there a bug on file somewhere to coordinate the investigation? -Terrence > -Jeff > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
