Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Cesar Matheus <cesar.matheus@telecom-paris.fr>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [BASIC QUESTION] Profiling tool for ffmpeg
Date: Mon, 24 Feb 2025 15:43:25 +0100 (CET)
Message-ID: <577271964.20142847.1740408205310.JavaMail.zimbra@telecom-paris.fr> (raw)

Hi, I'm a CS student working on an optimisation of the ebur128 filter. First I'm looking for the nicest way to get information on code performance.
I saw  that the configuration flag   "--enable-linux-perf"      enables Linux Performance Monitor API, I've been using the perf tool with the following commands for example :

./perf record -F 99 -a -g --call-graph dwarf ./ffmpeg -i test.wav -vn -af loudnorm=print_format=summary:dual_mono=true -f null /dev/null

but I'm not quite satisfate with the result. 

Do you have any advice on how to properly extract informations such as execution time, function call graph etc.. in such a case using profiling tool (perf or gprof for example ?

Thank you very much,
César Mathéus
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

             reply	other threads:[~2025-02-24 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 14:43 Cesar Matheus [this message]
2025-02-24 14:44 ` Kieran Kunhya via ffmpeg-devel
2025-02-24 14:53 ` Devin Heitmueller
2025-02-24 17:03   ` Stone Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=577271964.20142847.1740408205310.JavaMail.zimbra@telecom-paris.fr \
    --to=cesar.matheus@telecom-paris.fr \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git