Education/Projects/ProcessingForTheWeb/Performance: Difference between revisions

'''P100) Canvas Stalling''' - Canvas stalls with mouse movement, hardware interupts, CPU spikes etc and appears to stall at regular intervals when idle. GC suggested as likely cause. This behavior does not seem to be present in Safari or Chrome.<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>  

'''P200) 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></blockquote><blockquote></blockquote>  

'''P300) Drop Frames''' - Firefox does not appear to have any mechanism by which to drop frames whereas Chrome most certainly does. It is possible that some of the perceived speed in Chrome's Canvas implementation is due to it's ability to drop frames that could not render in time. Ideally this kind of behavior should be switchable as it would not be desired for an application requiring the capture of every single frame across a given range of data, that was intended for post-production, whereas it would be very desirable for games and interactive UI elements.<br>  

<blockquote>'''Example:''' http://hyper-metrix.com/processing-js/docs/?page=Drop%20Frames%20and%20For%20Loops%20-%20Chrome%20vs%20FireFox<br> <br></blockquote><blockquote></blockquote>