<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Control Loops on Precomputing.com</title>
    <link>https://precomputing.com/tags/control-loops/</link>
    <description>Recent content in Control Loops on Precomputing.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 01 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://precomputing.com/tags/control-loops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AltSql Realtime Meets a 10 ms Deadline on a Simulated Flash Chip That Takes 45 ms to Erase</title>
      <link>https://precomputing.com/altsql-realtime-meets-a-10-ms-deadline-on-a-simulated-flash-chip-that-takes-45-ms-to-erase/</link>
      <pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://precomputing.com/altsql-realtime-meets-a-10-ms-deadline-on-a-simulated-flash-chip-that-takes-45-ms-to-erase/</guid>
      <description>&lt;p&gt;A controller runs its loop 100 times a second. Every cycle it saves a value and logs a row, and those writes have to finish within 10 ms. The trouble is the flash chip. Before it can reuse a sector it has to erase it, and on the chip the demo models, a Winbond W25Q32FV, an erase takes 45 ms typically and up to 400 ms at the slowest its datasheet allows. A storage engine that erases inside a write will, sooner or later, make the loop miss its deadline.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
