Education/Projects/ProcessingForTheWeb/Performance: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
Line 1: Line 1:
I have been looking at old test-cases for Canvas bugs which I discovered and submitted info on: such as Global Alpha, ArcTo, etc. Things seem to have been fixed, and it is very comforting to witness Mozilla developers having moved things forward over time.  
I have been looking at old test-cases for Canvas bugs which I discovered and submitted info on: such as Global Alpha, ArcTo, etc. Things seem to have been fixed, and it is very comforting to witness Mozilla developers having moved things forward over time.  


There are other bugs/performance issues and features which need addressing. The lists that follow will have test cases added shortly and I will be trying to link these to old bugzilla reports so we can get some outstanding threads closed down.  
There are other bugs/performance issues and features which need addressing. The lists that follow will have test cases added shortly and I will be trying to link these to old bugzilla reports so we can get some outstanding threads closed down. <br>


'''Performance Issues:'''
<br>


#Canvas drawing slower when mouse rolls over.
== <br> '''Performance Issues:<br><br> '''  ==
#Canvas jerking/choking at regular intervals.
#Getting / Setting pixel arrays very slow! - Currently pixels are being passed to a JS array. Some kind of abstraction is needed to act as an API to the JS developer, that while acting like an array. is really running at machine level. See: [https://bugzilla.mozilla.org/show_bug.cgi?id=499201 https://bugzilla.mozilla.org/show_bug.cgi?id=499201]<br>


<br>  
'''A) Canvas Stalling''' - Canvas stalls with mouse movement, hardware interupts, CPU spikes etc and appears to stall at regular intervals when idle.<br>
<blockquote>'''Test Case:'''<br> http://hyper-metrix.com/git/canvas-lab/performance/stall-sensor.html<br> '''Bugzilla:'''<br> https://bugzilla.mozilla.org/show_bug.cgi?id=504640<br> https://bugzilla.mozilla.org/show_bug.cgi?id=482204<br> https://bugzilla.mozilla.org/show_bug.cgi?id=504640 <br> </blockquote>
'''C) Slow Getting &amp; Setting of Pixel Array''' - Currently pixels are being passed to a JS array. Some kind of abstraction is needed to act as an API to the JS developer, that while acting like an array. is really running at machine level.<br>
<blockquote>
'''Test Case:''' to follow<br> '''Bugzilla:''' https://bugzilla.mozilla.org/show_bug.cgi?id=499201<br>
 
<br>
</blockquote>
== '''Bugs:'''  ==


'''Bugs:'''  
== <br>'''Feature Requests:<br>''' ==


<br> '''Features:'''
<br>

Revision as of 07:22, 5 October 2009

I have been looking at old test-cases for Canvas bugs which I discovered and submitted info on: such as Global Alpha, ArcTo, etc. Things seem to have been fixed, and it is very comforting to witness Mozilla developers having moved things forward over time.

There are other bugs/performance issues and features which need addressing. The lists that follow will have test cases added shortly and I will be trying to link these to old bugzilla reports so we can get some outstanding threads closed down.



Performance Issues:

A) Canvas Stalling - Canvas stalls with mouse movement, hardware interupts, CPU spikes etc and appears to stall at regular intervals when idle.

Test Case:
http://hyper-metrix.com/git/canvas-lab/performance/stall-sensor.html
Bugzilla:
https://bugzilla.mozilla.org/show_bug.cgi?id=504640
https://bugzilla.mozilla.org/show_bug.cgi?id=482204
https://bugzilla.mozilla.org/show_bug.cgi?id=504640

C) Slow Getting & Setting of Pixel Array - Currently pixels are being passed to a JS array. Some kind of abstraction is needed to act as an API to the JS developer, that while acting like an array. is really running at machine level.

Test Case: to follow
Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=499201


Bugs:


Feature Requests: