Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Jerome Martinez <jerome@mediaarea.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] vulkan: use a single command buffer per command buffer pool
Date: Thu, 17 Apr 2025 10:11:15 +0200
Message-ID: <ef9355d1-41d2-410f-8cab-ee196370eddb@mediaarea.net> (raw)
In-Reply-To: <20250416132612.19085-1-dev@lynne.ee>

Le 16/04/2025 à 15:26, Lynne a écrit :
> We violated the spec, which, despite the actual command buffer pool
> *not* being involved in any functions which require external synchronization
> of the pool, *require* external synchronization even if only the
> command buffers are used.
>
> This also has the effect of *significantly* speeding up execution
> in case command buffers are contended.

I can confirm a +6% on 16-bit content on a RTX 4070 Ti.
With a 2K 16-slice content:
- It was freezing after ~300 frames on a RTX 4070 Ti, now it runs slowly 
but smoothly,
- The UI was frozen on a RTX 3050, still some kind of freeze with this 
patch but it is better (especially with -thread 1)

no regression found.
_______________________________________________
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-04-17  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 13:26 Lynne
2025-04-17  8:11 ` Jerome Martinez [this message]

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=ef9355d1-41d2-410f-8cab-ee196370eddb@mediaarea.net \
    --to=jerome@mediaarea.net \
    --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