<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jonas Losis</title>
    <description>The latest articles on DEV Community by Jonas Losis (@sintorio).</description>
    <link>https://dev.to/sintorio</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3770560%2Fa054aca0-9797-4e3c-92cf-e4769d5015fe.png</url>
      <title>DEV Community: Jonas Losis</title>
      <link>https://dev.to/sintorio</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sintorio"/>
    <language>en</language>
    <item>
      <title>How I built a parallel video pipeline on RTX 5090s to kill cloud processing lag</title>
      <dc:creator>Jonas Losis</dc:creator>
      <pubDate>Fri, 13 Feb 2026 09:31:19 +0000</pubDate>
      <link>https://dev.to/sintorio/how-i-built-a-parallel-video-pipeline-on-rtx-5090s-to-kill-cloud-processing-lag-3ofl</link>
      <guid>https://dev.to/sintorio/how-i-built-a-parallel-video-pipeline-on-rtx-5090s-to-kill-cloud-processing-lag-3ofl</guid>
      <description>&lt;p&gt;Most AI video tools today are just wrappers around shared cloud GPU instances. When you upload a long video, your file sits in a queue behind hundreds of other jobs, which is why "AI clipping" often takes 40 minutes. The AI itself isn't slow, but the infrastructure is.&lt;/p&gt;

&lt;p&gt;I decided to build Sintorio by moving away from rented cloud instances and running on a dedicated cluster of RTX 5090 GPUs that I own and operate. To hit the speeds I wanted, I had to optimize every layer of the stack.&lt;/p&gt;

&lt;p&gt;For transcription, I used faster-whisper with a batched inference pipeline. The 25.7GB of VRAM on the 5090 allows for a much larger batch size than older cards, which sustains about 18x real-time throughput. I also moved face tracking from the CPU to the GPU using SCRFD on ONNX Runtime, which dropped frame processing time from 20ms to about 2ms.&lt;/p&gt;

&lt;p&gt;The rendering itself happens in parallel using a producer-consumer model. Clips start rendering via hardware encoding the moment a viral segment is identified, so the system never sits idle waiting for the next step.&lt;/p&gt;

&lt;p&gt;The end result is that a one-hour 4K video can be processed and branded in under two minutes. Since I run the hardware ourselves, it also allows for a zero data retention policy—videos are auto-deleted immediately after the session because I don't need to train models on user data.&lt;/p&gt;

&lt;p&gt;I'm currently offering a lifetime deal to help fund the next rack of 5090s. I would love to hear from anyone else working on inference optimization for the Blackwell architecture or running their own GPU setups.&lt;/p&gt;

&lt;p&gt;I’m currently offering a €79 Lifetime Deal to help fund the next rack of 5090s. No investors, just hardware and coffee.&lt;/p&gt;

&lt;p&gt;I'd love to hear how others are optimizing inference on the 50-series cards!&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>ai</category>
      <category>python</category>
      <category>mojo</category>
    </item>
  </channel>
</rss>
