I want to second Dave's point here -- it's important if we could preserve the order between processes so that we could work on Gaia System bugs.
I also want to say if we could reflect the log level in Gecko, the Console API have already design to have a set of levels: https://developer.mozilla.org/en-US/docs/Web/API/console - console.log - console.info - console.warn - console.error Not sure four level is enough though. It's probably make sense to establish an agreement among Gaia developers on how to utilize these functions (but first we should be allowed to use them). On Fri, Aug 29, 2014 at 1:50 AM, Dave Hylands <[email protected]> wrote: > Even if we send the log to the parent, I'd still like to see the logcat > happen in the child in the thread that originally issues the log. > > This accomplishes 2 things: > > 1 - logcat records the PID and TID of the logger. I've found this to be > extremely useful information which would be lost. in logcat if the logging > is done in the parent. > > 2 - If you do the logcat in the parent you get out-of-sequence logs. The > parents logs will be logged with lower latency than the childs, which causes > weird logs. When the child does the logging, the sequence is preserved. This > is extremely useful when logging any type of activity which is split between > the child and parent. > > Dave Hylands > > ________________________________ > > From: "Jonas Sicking" <[email protected]> > To: "Gabriele Svelto" <[email protected]> > Cc: "Eric Rahm" <[email protected]>, [email protected], > "Dave Hylands" <[email protected]> > Sent: Thursday, August 28, 2014 10:09:05 AM > > Subject: Re: [b2g] Log collection needs improvement > > On Thu, Aug 28, 2014 at 1:39 AM, Gabriele Svelto <[email protected]> > wrote: >> IPC is quite expensive in general on our implementation so even when >> it's non-blocking it does have a measurable performance impact on >> single-core devices. Bug 915733 [1] contains more information on this. > > There's a lot of disagreement on this. So far no one has been able to > show a profile where this is the case. Every time that we have > performance with IPC it is because the parent process is busy doing > other things which means that it takes longer than we want to get a > response. > > I.e. the problem is one of latency rather than throughput in every > profile that anyone has been able to produce. > > However for logging we don't need to get any response. And it doesn't > matter if the logging message appears a few ms later than when the > logging call was made. So this is not a problem. > > If you have a profile that can show otherwise, please do share. > > / Jonas > > > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > -- Tim Guan-tin Chien, Engineering Manager and Front-end Lead, Firefox OS, Mozilla Corp. (Taiwan) _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
