Hey Paul, I think that visualization lines up with what will happen with performance.measure(), showing durations instead of markers (which use for performance.mark()). The difficult situation is aggregating markers and durations across processes and having them represented as if they occurred within a single page. Not to mention these APIs can also be used to aggregate performance data which we do analysis in using external tools like Datazilla. I think those are the main differences between the APIs, and why we need another mechanism for linking between processes.
My instinct tells me that upon creating a performance.mark/measure, we should be able to store some additional metadata with the instance that contains the URL of the page/app generating the indicator. We can then use this in the System app/parent process to aggregate all markers of a certain origin to build out a timeline, etc. Just throwing ideas out there, as I have no idea how we would actually annotate a marker without changing the spec. Thanks, *Eli Perelman* Software Engineer, Firefox OS On Thu, Oct 16, 2014 at 11:10 AM, <[email protected]> wrote: > We are doing exactly that but with a different API in the timeline. > > The Console API comes with 2 methods: > - console.time(aStr); > - console.timeEnd(aStr); > > It looks like this in Firefox' timeline: > http://i.imgur.com/EqHTQde.png > http://i.imgur.com/TUSdORn.png > > Bug 1050502 (about to land) will add a marker in the timeline when timeEnd > is called. > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
