From: Daniel Pittman <slippycheeze@google.com>
To: Evgeny Zajcev <lg.zevlg@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: excessively slow image animation
Date: Tue, 26 Feb 2019 16:18:21 -0500 [thread overview]
Message-ID: <CAC45yQtMLGipuFtrPuJADUcDSLvTK91gsMfDMaX6SQcgvL95aQ@mail.gmail.com> (raw)
In-Reply-To: <CAO=W_ZrUUDM3aaNgf9X84Z0vapDWd8gT=dS02sdWqx7anXP_tw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
On Wed, Feb 13, 2019 at 9:56 AM Evgeny Zajcev <lg.zevlg@gmail.com> wrote:
> I've got multi frame image at http://lgarc.narod.ru/giphy.mp4
> 18 seconds to show every frame
>
Time to fully extract the images from that (cold cache) on my laptop was ~
30 seconds. It contains one key frame, the very first, and everything else
is a P frame, so to decode frame 20 you need to run forward applying 19
frames worth of data from the start.
If the components were being cached or generated independently – highly
likely, I suspect – then that time-cost would be paid the first time. A
grand total of 18 seconds to do that processing doesn't actually sound
unreasonable to me, honestly, given that decoding all those frames in
individual processes takes ~ 5.35 seconds total on my machine. It wouldn't
take much inefficiency on top of that to bring it up to that rate.
>
[-- Attachment #2: Type: text/html, Size: 1612 bytes --]
next prev parent reply other threads:[~2019-02-26 21:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 14:39 excessively slow image animation Evgeny Zajcev
2019-02-13 17:03 ` Lars Ingebrigtsen
2019-02-13 23:14 ` Alan Third
2019-02-13 23:29 ` Evgeny Zajcev
2019-02-14 18:21 ` Alan Third
2019-02-14 18:41 ` Evgeny Zajcev
2019-02-14 0:30 ` Evgeny Zajcev
2019-02-14 4:30 ` Stefan Monnier
2019-02-26 21:18 ` Daniel Pittman [this message]
2019-02-26 21:50 ` Evgeny Zajcev
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=CAC45yQtMLGipuFtrPuJADUcDSLvTK91gsMfDMaX6SQcgvL95aQ@mail.gmail.com \
--to=slippycheeze@google.com \
--cc=emacs-devel@gnu.org \
--cc=lg.zevlg@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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.