<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Video-Transcoding on Kuldeep Pisda</title><link>https://kdpisda.in/tag/video-transcoding/</link><description>Recent content in Video-Transcoding on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 04 Apr 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/video-transcoding/index.xml" rel="self" type="application/rss+xml"/><item><title>150 Videos a Day Buried Our CPU Transcoders, So I Stopped Encoding In-House</title><link>https://kdpisda.in/cpu-transcoding-too-slow-aws-mediaconvert/</link><pubDate>Sat, 04 Apr 2026 10:00:00 +0530</pubDate><guid>https://kdpisda.in/cpu-transcoding-too-slow-aws-mediaconvert/</guid><description>&lt;p&gt;In the last chapter we owned the whole video pipeline: content uploaded to an S3 ingest bucket, a Celery worker on ECS ran ffmpeg to build the adaptive-bitrate ladder, and CloudFront served the HLS chunks. It worked beautifully the day I demoed it with three test videos. Then the content team found the bulk uploader.&lt;/p&gt;
&lt;p&gt;I opened Grafana on a Tuesday and the &lt;code&gt;transcode_video&lt;/code&gt; queue depth was a straight diagonal line, climbing since nine that morning. Not a spike that drains — a line that only went up. The team had discovered they could select a course&amp;rsquo;s entire back-catalogue and push it in one sitting, and they were doing exactly what a good content team should do: 150-plus videos before lunch. My CPU workers were going to be chewing on that pile until Friday.&lt;/p&gt;</description></item></channel></rss>