Re: Measuring DOM performance

On 10/21/09 4:34 AM, Jean-Marc Desperrier wrote:
> It obviously measures js performance in addition to DOM performance.

Well, hold on.  When we talk about "DOM performance" this means "DOM 
performance as experienced by web pages".  Which means including the 
performance of the JS-to-C++ bridge, in particular.

> A first step is to disable jit to not measures the jit engine ability to
> jit the dromaeo code

This affects the JS-to-C++ bridge performance, so it's not clear to me 
that this is the right thing to do.

> Do you need to measure the performance of every DOM operation ?

Since the set of possible operations (meaning DOM method calls and 
arguments and contexts for the calls) is infinite, this is not really 
doable.  I'd like us to not limit what we measure, though, which is 
easier if we're not just measuring a single number.

> Of the most commonly used ones on the web ?

This is a bare minimum, but do we even know what DOM operations are 
commonly used?  And the contexts they're used in?

> Is measuring a short set of simple DOM operation a good enough proxy ?

As a start it might be; that's where I sort of view dromaeo as being 
right now, if you ignore its js framework tests.  The js framework tests 
are closer to "do this operation with more different arguments and in 
different contexts".

-Boris