Linked by Thom Holwerda on Sat 16th Dec 2006 16:58 UTC, submitted by Hakime
Thread beginning with comment 193392
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2006-10-12
Encoding HDTV is a CPU-intensive process with a limited number of potential bottlenecks: simply pointing the finger at ‘the kernel’ isn't in the slightest bit useful, all told.
Realistically, there are only three real places that something like that could suffer: an I/O bottleneck (Linux could be more efficient at buffering than OS X), a memory-management issue (was XNU swapping when Linux wasn't, for example?), or a scheduling problem coupled with the two previous: for example, was there a resource over-allocation applied to the encoding process which makes task switches slower than they should be (i.e., causing a slow-down in both overall encoding performance and interactivity)?
What you really should be doing is profiling the encoder on both platforms to find out what's slowing it down: with a process that actually uses the kernel as infrequently is this, it wouldn't be particularly difficult to do and perform a real comparison.