On 03/27/2011 01:58 PM, Ronald S. Bultje wrote: > Ideas: > - run ffmpeg decoding a typical h264 file through a profiler (linux: > valgrind + kcachegrind, macosx: shark) > - identify the parts of ffmpeg that take a lot of processing time, and > where you see possibilities to optimize > - get coding, and profile the function + all of ffmpeg before/after to > test to see how much faster it got
Other useful tools might be: - dtrace (Instruments in macosx is a relatively easy way to use it) - perf2 (Linux only, sort of easier and nicer oprofile) lu -- Luca Barbato Gentoo/linux http://dev.gentoo.org/~lu_zero _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
