BFS vs. mainline scheduler benchmarks and measurements
BFS vs. mainline scheduler benchmarks and measurements
Posted Sep 7, 2009 14:41 UTC (Mon) by cortana (subscriber, #24596)In reply to: BFS vs. mainline scheduler benchmarks and measurements by ldarby
Parent article: BFS vs. mainline scheduler benchmarks and measurements
All mplayer has to do is decode video to YUV and then hand the picture off to the video card, which scales it to fit the screen, etc, in hardware.
Flash has to decode the video, then convert it to RGB, then combine it with other graphical elements created on the fly by a flash movie written by someone who has no idea how to program efficiently, then somehow get the result to the screen, and the methods for doing this for RGB data on Linux are buggy, inefficient, and hardware-dependent (when they even exist in the first place!)
Having said that, there is a great deal of room for improvement on the Flash side as well. One of the people who works for Adobe in porting the Flash player to Linux--a thankless task!--occasionally posts to a blog where he details interesting problems he runs into. Some interesting posts include:
http://blogs.adobe.com/penguin.swf/2008/05/
http://blogs.adobe.com/penguin.swf/2006/10/
http://blogs.adobe.com/penguin.swf/2006/09/#a001737
and another that I can't find right now where he writes about how the Windows version is accelerated by assembly code which has been optimised for years, but the Linux version can't because it's all locked away in Microsoft's assembler source format or something.
