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
