From: Sidd via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Sidd <sid9.karanam@gmail.com>
Subject: [FFmpeg-devel] [Question] Testing and evaluating runtime performance of functions
Date: Mon, 17 Nov 2025 16:23:03 +0530
Message-ID: <CABM86pxUuTWB081N2Zhqx90xwi7XTDd1OHBffSo4ef9vEC2sHw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
I have been going through some code and found a couple of FIXME's that
mention the section of code to be "slow" and I was just curious since
I am relatively new to most kinds of profiling, how do you evaluate
this and if anybody were to come up with a patch for this, how can
they reliably show speedups in this?
I am assuming simply using valgrind or perf to cpu profile (on linux
atleast) can do a decent job showcasing certain metrics like cycles
spent, time of execution so on but I would appreciate it if I can get
some clarity on this, as I am unsure of what is expected and the usual
practice here.
PS: Sorry for double mailing my patch. I was not aware that opening a
PR would do the same.
[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 58665 bytes --]
[-- Attachment #3: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-11-17 10:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABM86pxUuTWB081N2Zhqx90xwi7XTDd1OHBffSo4ef9vEC2sHw@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=sid9.karanam@gmail.com \
/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