Catle Wolfenstein ( continued ) — OZONE Asylum, home of the Mad Scientists

DHTML/Javascript

Catle Wolfenstein ( continued )

This page's ID: 29953

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	[b]argo navis:[/b] the back map ? [b]wrayal:[/b] Just had a look in Op9.5 b9721 and FF3b2. Of course Castle Wolfenstein was never running in both browsers at the same time. [b]Op9.5 [small]b9721[/small][/b] [small]( with 16 tabs open )[/small][ulist]* Usually spend ~17 ms with the occasionnal peak at ~44 ms on the lines 8->11 , and ~1 ms on the lines 12->16 * There is no reflow in the main function. A reflow occurs between two calls though but it's reported as taking 0-1 ms. I'll have to ask some coleagues but that might be the blit when the function falls out of scope Not sure. * The time spent on the lines 8->16 is constant regardless of the visibility of the renderArea. * When the renderArea is NOT visible, the time between two calls is that of the setInteral + ~30 ms +- 10ms. * When the renderArea is visible, the time between two calls is that of the setInteral + ~30 ms +- 10ms. * Commenting out the style updates in the lines 8->11 down the time spent there to ~9 ms[/ulist] [b]FF3b2[/b] [small]( with a single tab open )[/small][ulist]* spend ~46 ms +- 6 ms on the lines 8->11 , and ~1 ms on the lines 12->16. * I don't know how many reflows occurs * The time spent on the lines 8->16 is constant regardless of the visibility of the renderArea. * When the renderArea is NOT visible, the time between two calls is that of the setInteral. * When the renderArea is visible, the time between two calls is that of the setInteral + ~100 ms +- 20ms. * Commenting out the style updates in the lines 8->11 down the time spent there to ~25 +- 6 ms[/ulist] [b]SF3b4[/b] [small]( with a single tab open )[/small][ulist]* spend ~20 ms on the lines 8->11 , and ~1 ms on the lines 12->16. * I don't know how many reflows occurs * The time spent on the lines 8->16 is constant regardless of the visibility of the renderArea. * When the renderArea is NOT visible, the time between two calls is that of the setInteral + ~15 ms. * When the renderArea is visible, the time between two calls is that of the setInteral + ~50 +- 10 ms. * Commenting out the style updates in the lines 8->11 down the time spent there to ~12 ms[/ulist] Looks like the big bottleneck in FF3b2 is the blit. Since I don't know how many reflow occur in FF, I can't know for sure if it's purely a blit issue or if this is more serious like some CSS updates not being optimized and a/some reflow occurs although none of the style property I touch should trigger a one. Alas it's not the only thing going wrong. JavaScript itself seem a little slow with a 3 fold difference on pure JavaScript processing of the lines 8->11. It might be the extensive use of variables with different scope. I'll try to figure this out. Does anyone have some experience in that kind optimization ? [b]Scott[/b] Schiller might know. Btw, I'm giving out a unicorn to the first one who can tell me how to get the number of reflows and the time spent reflowing in Firefox, without recompiling it. And I top the offer with a puppy if you can get the same info for the redraws. [url=http://www.p01.org/][img]http://poi.ribbon.free.fr/files/p01_ozoneasylum_sig_galaxy.gif[/img][/url] [small](Edited by [url=http://www.ozoneasylum.com/user/2185]poi[/url] on 02-02-2008 16:36)[/small] Loading...
Options:	Enable Slimies Enable Linkwords

« Backwards — Onwards »

Show Forum Drop Down Menu