[Wtr-general] downloadtime and render_time
Paul Rogers
paul.rogers at shaw.ca
Wed Oct 18 00:32:19 EDT 2006
I was mistaken in how this works -it is a lot harder than I thought,
especially for frames. I think the non frames case is do-able, but then we
have different behaviour.
Paul
----- Original Message -----
From: "Bret Pettichord" <bret at pettichord.com>
To: <wtr-general at rubyforge.org>
Sent: Tuesday, October 17, 2006 3:48 PM
Subject: Re: [Wtr-general] downloadtime and render_time
> Paul Rogers wrote:
>> I think IE separates the download time and render time for each page. I
>> always thought that for frames we needed something like
>>
>> ie.download_time # time for everything, all frames download, render
>> ie.download_times[xx] # download time for specific item, xx could be
>> frame name, id, index
>>
>> I'll see what I can do.
>>
> Hmm. Right now Watir::IE#wait computes the @down_load_time simply by
> measuring how long it waits. Are you suggesting that IE itself also
> stores download timing information?
>
> It seems to me that breaking down this information by frame would be
> highly imprecise and misleading. The problem is that the different
> frames are typically loaded concurrently. For example, imaging that
> Frame1 takes 4 seconds to load and that Frame2, which is loading at the
> same time, takes 2 seconds. IE#wait would wait for 4 seconds for Frame1
> and then an additional 0 seconds for Frame2. But if it were the other
> way around, it would wait 2 seconds for Frame2 and then 2 more seconds
> for frame4. So what would be the correct breakdown of the down-load-time
> for the frames? Would you spawn a separate wait-thread for each frame to
> provide a more accurate means of measurement?
>
> Bret
> _______________________________________________
> Wtr-general mailing list
> Wtr-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/wtr-general
>
More information about the Wtr-general
mailing list