WinCE Timers

[patrick.east]

Hello,

I am working on the WinCE webkit port, and I am having some weird
performance issues with canvas animation. While rendering a page such
as this: http://themaninblue.com/experiment/AnimationBenchmark/canvas/?particles=1
I get 50-100 WM_TIMER messages that are ~10ms apart between WM_PAINT
messages. Any ideas as to what those timers are doing and why so much
time is being spent doing that between paints?

Thanks!

(I'm on #webkit as PeterPatrick, either post here or message me there
if you know anything about this)

[Rodney Dowdall]

Hello Patrick

Looking at the source to the webpage, it looks like it is firing a timer every millisecond.  If I had to venture a guess, the problem is that webkit can't keep up, so your timers queue up.  
Are you using the precision timers for wince?  If you aren't,  then the minimum timer resolution for wince is ten milliseconds.  I believe that wince gives precedence to timer and user events, so if you were handling the timer every milliseconds, then you wouldn't see anything draw.

Also, whatever the page is trying to do between paints may be too intense for the system to handle.

Just a couple of thoughts,
Rodney

www.cranksoftware.com

--
You received this message because you are subscribed to the Google Groups "Windows CE WebKit" group.
To post to this group, send email to wince...@googlegroups.com.
To unsubscribe from this group, send email to wincewebkit...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/wincewebkit?hl=en.

[patrick.east]

Alright so I got it working, turns out it was an issue with the
CurrentTime.cpp where we used the QUERY_PERFORMANCE_COUNTER, by
turning that off we got rid of the huge gaps between paints. We now
see 10+ fps on the same page instead of 3.

-Patrick

On Nov 13, 3:31 pm, "Rodney Dowdall" <rdowd...@cranksoftware.com>
wrote:

> Hello Patrick
>
> Looking at the source to the webpage, it looks like it is firing a timer every millisecond.  If I had to venture a guess, the problem is that webkit can't keep up, so your timers queue up.
> Are you using the precision timers for wince?  If you aren't,  then the minimum timer resolution for wince is ten milliseconds.  I believe that wince gives precedence to timer and user events, so if you were handling the timer every milliseconds, then you wouldn't see anything draw.
>
> Also, whatever the page is trying to do between paints may be too intense for the system to handle.
>
> Just a couple of thoughts,
> Rodney
>
> www.cranksoftware.com
>
> ----- Reply message -----
> From: "patrick.east" <east.patr...@gmail.com>
> To: "Windows CE WebKit" <wince...@googlegroups.com>
> Subject: [wincewebkit] WinCE Timers
> Date: Fri, Nov 11, 2011 7:16 pm
>
> Hello,
>
> I am working on the WinCE webkit port, and I am having some weird
> performance issues with canvas animation. While rendering a page such

> as this:http://themaninblue.com/experiment/AnimationBenchmark/canvas/?particl...