In general, Flash is not hard on the processor; the content of Flash is highly processor dependent. People usually don’t use Flash to display static text and bitmap images, they use it for vector animation, as well as video and RIA with components with a custom shell, and the processor occupies the layout of all these vectors and gradients and alpha channels - regardless of whether you use whether you are Flash or HTML5 or Silverlight or JavaFX or whatever. Feel free to view the demo of this animation comparison and see how CPU usage in HTML5 version comes down to the Flash version. The results vary widely between OS and browsers, but for me (winXP / firefox) the Flash version uses about the same processor as the canvas version (~ 50%), giving a little more than double FPS.
The second answer relates to video in particular, and the answer is: no matter what technology you use to display the video, only two things really affect the use of the CPU: the codec and whether its hardware acceleration is accelerated. You can test H264 video between browsers and the OS and Flash / HTML5 ( and people have done it ), and you will find that the CPU is low, video hardware acceleration, and this is high when it is not like inside or outside of Flash. Thus, there is no problem whether the Flash video is connected to the processor, the only question is whether the Flash video uses HWA or not. Check the full link information, but mostly if you are not using OSX / Safari, Flash video uses the same processor or fewer other parameters.
By the way, if you are also wondering why Flash has historically used more processors for Mac than on PC, even for non-video content, see here for many details - both about why this was worse in the past, and why It improves with Flash 10.1. The quick version is that Apple has added new and more effective ways to connect plug-ins to the browser.
fenomas
source share