W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2010

Re: [WebTiming] HTMLElement timing

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 18 Feb 2010 13:44:44 -0800
Message-ID: <63df84f1002181344i1bcbd0b9w7c9603f9655254d3@mail.gmail.com>
To: James Robinson <jamesr@google.com>
Cc: Zhiheng Wang <zhihengw@google.com>, "lenny.rachitsky" <lenny.rachitsky@webmetrics.com>, public-webapps@w3.org
On Wed, Feb 17, 2010 at 10:36 PM, James Robinson <jamesr@google.com> wrote:
> * What precisely does 'parse' time mean for each element?  For example, on a
> <script> tag does parse time include parsing the script itself, or executing
> it as well?  What about for JS engines that do not distinguish between the
> two?

Then there is also things like JITs, which at least in some engines
run lazily. So a function isn't JITted until the first time it runs.
Which may or may not be long after the <script> has executed. In
firefox things are even worse because a function isn't "traced" until
we've determined that it's a "hot" path, i.e. that it's run several

/ Jonas
Received on Thursday, 18 February 2010 21:45:39 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:22 UTC