[MPlayer-dev-eng] MplayerXP vs Mplayer. Hall of truth.
Brian J. Murrell
e84cecdf7ef5e3ae83c2a600ae7c555e at interlinx.bc.ca
Mon Mar 18 10:59:42 CET 2002
On Sun, Mar 17, 2002 at 05:20:37PM +0100, Gábor Lénárt wrote:
>
> BTW, I don't understand why threading makes things faster (of course on
> single CPU system, on SMP it's true of course).
Because threading might take some code out of a(n I/O) "blocked" path
and put it into an executable path.
> Maintaining multiple contexts
> by scheduler makes a bit SLOWER not faster. The fastest possible way to
> implement an algorithm on UP systems is using only ONE thread (of course
> it can be true that it makes it smoother a bit but also it will be slower).
You are right in all of this, as long as the one thread is free of I/O
blocking.
If Nick really has found a 200-300% efficiency gain with threading,
what he likely has done is found tasks in "old" mplayer core that
block other tasks from happening (such as decoding and buffering
frames).
b.
--
Brian J. Murrell
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-dev-eng/attachments/20020318/ddc9dc33/attachment.pgp>
More information about the MPlayer-dev-eng
mailing list