On 2/10/2014, 10:06 AM, David Rajchenbach-Teller wrote:
On 2/10/14 2:43 PM, Benjamin Smedberg wrote:
On 2/7/2014 10:31 AM, David Rajchenbach-Teller wrote:
Since main thread I/O keeps being added to the tree, for good or bad
reasons, I believe that we should adopt a convention of tagging
legitimate main thread I/O.
When you say "tagging" do you mean just code comments, or some other
marker that we can use in automated tooling to root out "untagged"
main-thread I/O?
I am thinking about code comments.
However, BenWa's suggestion of formalizing this as labels for the
profiler sounds useful, too.
My suggestion is to try to do more than just code comments. Then maybe,
*maybe*, we will some day have a way to run Firefox in a mode which
would detect when main thread IO happens, and provide some kind of
useful information for us to fix it. We can employ such a technique as
a tool to make it an error to add more main thread IO in my imaginary
utopia. :-)
Cheers,
Ehsan
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
