Slow animated PNG transcoding
We are seeing transcoding times hundreds of times slower than what a local computer can do with FFMPEG when converting animated PNG files to other file types.
A 6.5mb animated PNG file will take 25 seconds to return a HEAD request. Larger files will increase this time but single frame PNGs will encode very fast. It seems like the more frames a PNG has the slower it is transcoding.
We are wondering if there is something we can do to get these transcoding times down to something closer to what we can do with FFMPEG and if there is something about the system that we should be keeping in mind when uploading them to Cloudinary? Which file types transcode faster than others, what types of files does Cloudinary optimize for? Are there additional flags we can set to work around these issues?
-
Here is an example file we are seeing these times with.
https://assets.ppassets.com/p-6J32eUFRVDDmvXdET4cuak/flyer/ugc_background/original
It is hard to do an apples to apples test with another file type but if you convert this file to a GIF (it will be a smaller file) but the transcoding happens in around a single seconds, and upload larger GIF files roughly the size of the one above the time is a a few seconds but never as long as the animated PNGs
0 -
Hi,
Thanks for your message.
I was able to find that request in our logs and it seems that the transcoding part took ~12.5 seconds and the whole request completed in just under 13s.
Do you mind sharing some more details on your general workflow with APNGs - For example, when uploading to Cloudinary do you need to keep the files as APNG and create a derived GIF version? Will you need to create other derivatives such as animated WebP? Would it be an option to perform the transcoding on upload such as by using incoming transformations?
This information would help us fully understand your expected workflow and with that, we could then explore the best ways to optimise this flow.
Best regards,
Aleksandar
0
Post is closed for comments.
Comments
2 comments