Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Performances improvement in "image_copy_plane"
Date: Wed, 13 Jul 2022 13:15:59 -0300
Message-ID: <3dd32061-2748-8223-eeac-b9a90780cdb1@gmail.com> (raw)
In-Reply-To: <606778079.1512531.1657727656800@mail.yahoo.com>

On 7/13/2022 12:54 PM, Marco Vianini wrote:
> Sorry, my mail client was using html format.
> I hope now the mail will be sent correctly.
> 
> 
> You can get a very big improvement of performances in the special (but very likely) case of: "(dst_linesize == bytewidth && src_linesize == bytewidth)"
> 
> In this case in fact We can "Coalesce rows", that is using ONLY ONE MEMCPY, instead of a smaller memcpy for every row (that is looping for height times).
> 
> Code:
> "
> static void image_copy_plane(uint8_t       *dst, ptrdiff_t dst_linesize,
>                               const uint8_t *src, ptrdiff_t src_linesize,
>                               ptrdiff_t bytewidth, int height)
> {
>      if (!dst || !src)
>          return;
>      av_assert0(abs(src_linesize) >= bytewidth);
>      av_assert0(abs(dst_linesize) >= bytewidth);
>      
>      /// MY PATCH START
>      /// Coalesce rows.
>      if (dst_linesize == bytewidth && src_linesize == bytewidth) {
>        bytewidth *= height;
>        height = 1;
>        src_linesize = dst_linesize = 0;
>      }
>      /// MY PATCH STOP
> 
>      for (;height > 0; height--) {
>          memcpy(dst, src, bytewidth);
>          dst += dst_linesize;
>          src += src_linesize;
>      }
> }
> "
> 
> 
> I did following tests on Windows 10 64bit.
> I compiled code in Release.
> I copied my pc camera frames 1000 times (resolution 1920x1080):
> 
> With Coalesce:
> copy_cnt=100  size=1920x1080 tot_time_copy(us)=36574 (average=365.74)
> copy_cnt=200  size=1920x1080 tot_time_copy(us)=78207 (average=391.035)
> copy_cnt=300  size=1920x1080 tot_time_copy(us)=122170(average=407.233)
> copy_cnt=400  size=1920x1080 tot_time_copy(us)=163678(average=409.195)
> copy_cnt=500  size=1920x1080 tot_time_copy(us)=201872(average=403.744)
> copy_cnt=600  size=1920x1080 tot_time_copy(us)=246174(average=410.29)
> copy_cnt=700  size=1920x1080 tot_time_copy(us)=287043(average=410.061)
> copy_cnt=800  size=1920x1080 tot_time_copy(us)=326462(average=408.077)
> copy_cnt=900  size=1920x1080 tot_time_copy(us)=356882(average=396.536)
> copy_cnt=1000 size=1920x1080 tot_time_copy(us)=394566(average=394.566)
> 
> Without Coalesce:
> copy_cnt=100  size=1920x1080 tot_time_copy(us)=44303 (average=443.03)
> copy_cnt=200  size=1920x1080 tot_time_copy(us)=100501(average=502.505)
> copy_cnt=300  size=1920x1080 tot_time_copy(us)=150097(average=500.323)
> copy_cnt=400  size=1920x1080 tot_time_copy(us)=201010(average=502.525)
> copy_cnt=500  size=1920x1080 tot_time_copy(us)=256818(average=513.636)
> copy_cnt=600  size=1920x1080 tot_time_copy(us)=303273(average=505.455)
> copy_cnt=700  size=1920x1080 tot_time_copy(us)=359152(average=513.074)
> copy_cnt=800  size=1920x1080 tot_time_copy(us)=414413(average=518.016)
> copy_cnt=900  size=1920x1080 tot_time_copy(us)=465315(average=517.017)
> copy_cnt=1000 size=1920x1080 tot_time_copy(us)=520381(average=520.381)
> 
> 
> I think the results are very good.
> What do you think about?

It looks like a good speed up, but we need a patch created with git 
format-patch that can be applied to the source tree to properly review 
this. Can you send that?
_______________________________________________
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:[~2022-07-13 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <632087708.1175797.1657705107285.ref@mail.yahoo.com>
2022-07-13  9:38 ` Marco Vianini
2022-07-13  9:54   ` Paul B Mahol
2022-07-13 14:53     ` Marco Vianini
2022-07-13 15:10       ` Paul B Mahol
2022-07-13 15:54         ` Marco Vianini
2022-07-13 16:15           ` James Almer [this message]
2022-07-14 12:48             ` Marco Vianini
2022-07-13 15:12   ` Timo Rothenpieler

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=3dd32061-2748-8223-eeac-b9a90780cdb1@gmail.com \
    --to=jamrial@gmail.com \
    --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