<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rendering on TaskFused.com</title>
    <link>https://taskfused.com/tags/rendering/</link>
    <description>Recent content in Rendering on TaskFused.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 18 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://taskfused.com/tags/rendering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Video Rendering Through a Deploy With TaskFused, the Job Moves to a New Worker</title>
      <link>https://taskfused.com/video-rendering-through-a-deploy-with-taskfused-the-job-moves-to-a-new-worker/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://taskfused.com/video-rendering-through-a-deploy-with-taskfused-the-job-moves-to-a-new-worker/</guid>
      <description>&lt;p&gt;A video app turns each upload into a 1080p preview. A render takes about four minutes of CPU. Deploys happen several times a day, and every deploy restarts the render workers. With a simple job runner, a render that was three minutes in when the deploy started is just gone. The user&amp;rsquo;s preview never appears, or someone has to notice and start it again.&lt;/p&gt;&#xA;&lt;p&gt;The same render is also asked for more than once. The uploader&amp;rsquo;s browser asks for the preview, the share page asks for it when the link is opened, and the mobile app asks when it syncs. They all want the same file.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
