<?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: Ali Ahmad</title>
    <description>The latest articles on DEV Community by Ali Ahmad (@updateotter).</description>
    <link>https://dev.to/updateotter</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4211233%2F79a934da-c9dc-4d95-8c9a-1c52cc3b6279.JPG</url>
      <title>DEV Community: Ali Ahmad</title>
      <link>https://dev.to/updateotter</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/updateotter"/>
    <language>en</language>
    <item>
      <title>Why your PSU needs headroom: GPU power spikes, peak CPU draw, and the 30% rule of thumb</title>
      <dc:creator>Ali Ahmad</dc:creator>
      <pubDate>Thu, 05 Nov 2026 13:16:31 +0000</pubDate>
      <link>https://dev.to/updateotter/why-your-psu-needs-headroom-gpu-power-spikes-peak-cpu-draw-and-the-30-rule-of-thumb-ek2</link>
      <guid>https://dev.to/updateotter/why-your-psu-needs-headroom-gpu-power-spikes-peak-cpu-draw-and-the-30-rule-of-thumb-ek2</guid>
      <description>&lt;p&gt;A lot of PC builders size their power supply like this: add the CPU's TDP to the GPU's TDP, add a bit for "the rest", and buy the nearest wattage. That usually &lt;em&gt;boots&lt;/em&gt;. The trouble shows up later, as a random black screen or reboot in the middle of a demanding game, while temperatures look fine and nothing in the logs explains it.&lt;/p&gt;

&lt;p&gt;Very often the cause is not average power. It is &lt;strong&gt;peak&lt;/strong&gt; power.&lt;/p&gt;

&lt;h2&gt;
  
  
  Average draw vs. what the PSU actually sees
&lt;/h2&gt;

&lt;p&gt;A monitoring tool that reports "GPU power: 220 W" is showing you an average over a sampling window, often hundreds of milliseconds. Modern GPUs change their power draw much faster than that. When a heavy frame starts, clocks and voltage jump and the card can pull well above its rated board power for a very short moment, a few milliseconds or less. These are usually called &lt;strong&gt;transient spikes&lt;/strong&gt; or &lt;strong&gt;power excursions&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Your software never sees them. Your PSU does. If a spike is large enough to trip the PSU's over-current or over-power protection, the PSU does exactly what it was designed to do: it shuts off. To you, that looks like a crash.&lt;/p&gt;

&lt;p&gt;This was widely reported with some high-end cards in the RTX 30 and RX 6000 generations, where systems with PSUs that looked "big enough" on paper shut down under load. It is one of the reasons the newer ATX 3.x PSU standard explicitly requires power supplies to tolerate short excursions above their rated output. An ATX 3.x unit helps, but it does not make a too-small PSU the right size.&lt;/p&gt;

&lt;h2&gt;
  
  
  The CPU number is also bigger than the box says
&lt;/h2&gt;

&lt;p&gt;On the CPU side, the number on the spec sheet is often not the number that matters:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Intel&lt;/strong&gt; lists a &lt;em&gt;Processor Base Power&lt;/em&gt; and a higher &lt;em&gt;Maximum Turbo Power&lt;/em&gt;. Under a sustained all-core load with default limits, the chip can run near the higher figure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AMD&lt;/strong&gt; desktop chips have a &lt;em&gt;TDP&lt;/em&gt; and a higher &lt;em&gt;PPT&lt;/em&gt; (Package Power Tracking) limit, which is the actual socket power ceiling.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you plan with the base or TDP number, you are planning for a CPU that is not running flat out. Games rarely load every core, but shader compilation, loading screens, and background tasks can.&lt;/p&gt;

&lt;h2&gt;
  
  
  Everything else adds up too
&lt;/h2&gt;

&lt;p&gt;RAM, SSDs, fans, RGB, the motherboard's own VRM losses, and USB devices are small individually. Together they can be 50 to 100 W, more on a full-featured board with lots of fans.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the "add ~30%" rule comes from
&lt;/h2&gt;

&lt;p&gt;Once you sum the realistic peak numbers (CPU peak limit + GPU rated board power + the rest), a common rule of thumb is to add roughly &lt;strong&gt;25 to 35%&lt;/strong&gt; on top and round up to the next standard PSU size. That margin covers:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Transient GPU spikes&lt;/strong&gt; that last too briefly to show up in software.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CPU and GPU peaking at the same time&lt;/strong&gt;, which the sum assumes but real loads sometimes exceed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ageing and heat&lt;/strong&gt;, since a PSU's real-world capacity at high ambient temperature is a bit lower than on day one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A quieter, cooler PSU&lt;/strong&gt;: most units are more efficient and quieter in the middle of their load range than near 100%.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;It is not about "wasting" watts. A 750 W PSU does not draw 750 W from the wall; it supplies whatever the system asks for. Extra headroom mostly costs a bit more up front.&lt;/p&gt;

&lt;h2&gt;
  
  
  A worked example
&lt;/h2&gt;

&lt;p&gt;Say you are pairing a Ryzen 7 7700X with an RTX 4070 Super:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Part&lt;/th&gt;
&lt;th&gt;Planning figure&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Ryzen 7 7700X&lt;/td&gt;
&lt;td&gt;142 W (PPT)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RTX 4070 Super&lt;/td&gt;
&lt;td&gt;220 W (board power)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RAM, 2 drives, 3 fans, motherboard&lt;/td&gt;
&lt;td&gt;~80 W&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Total&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;~443 W&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Add 30%: about 576 W. Round up: &lt;strong&gt;600 W&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Then do one more check: &lt;strong&gt;compare with the GPU maker's own recommended PSU wattage.&lt;/strong&gt; For this card NVIDIA suggests 650 W, so 650 W is the sensible floor. The vendor figure assumes a fairly power-hungry CPU, which is exactly why it is a good safety net.&lt;/p&gt;

&lt;p&gt;If your number lands between two sizes, pick the larger one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Use the CPU's &lt;strong&gt;peak&lt;/strong&gt; limit (Max Turbo Power / PPT), not base power or TDP.&lt;/li&gt;
&lt;li&gt;Use the GPU's rated board power, then add headroom for spikes.&lt;/li&gt;
&lt;li&gt;Add 25 to 35% and round &lt;strong&gt;up&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Never go below the GPU vendor's recommended PSU.&lt;/li&gt;
&lt;li&gt;Prefer a reputable ATX 3.x unit if you are buying new, and use the cables it ships with.&lt;/li&gt;
&lt;li&gt;Remember this is an estimate. Overclocking, silicon quality, room temperature and peripherals all move the real number.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you do not want to do the math by hand, I put together a free &lt;a href="https://computingskill.com/psu-calculator/" rel="noopener noreferrer"&gt;PSU wattage calculator&lt;/a&gt; that follows the same steps: it uses peak CPU limits, adds a 30% margin, rounds up to the next 50 W step, and never goes below the GPU maker's guidance. It is a planning estimate, not a lab measurement, so treat the result as the &lt;em&gt;minimum&lt;/em&gt; size to shop for.&lt;/p&gt;

&lt;p&gt;What PSU are you running, and have you ever chased a shutdown that turned out to be power? I am curious what others have seen.&lt;/p&gt;

</description>
      <category>hardware</category>
      <category>pcbuilding</category>
      <category>gaming</category>
      <category>beginners</category>
    </item>
    <item>
      <title>How I run a fan wiki for a fast-changing Roblox game from CSV files in git</title>
      <dc:creator>Ali Ahmad</dc:creator>
      <pubDate>Tue, 27 Oct 2026 15:34:28 +0000</pubDate>
      <link>https://dev.to/updateotter/how-i-run-a-fan-wiki-for-a-fast-changing-roblox-game-from-csv-files-in-git-58j8</link>
      <guid>https://dev.to/updateotter/how-i-run-a-fan-wiki-for-a-fast-changing-roblox-game-from-csv-files-in-git-58j8</guid>
      <description>&lt;p&gt;Steal an Egg is a Roblox game that came out on 25 July 2026. It gets a big update about once a week, plus smaller fixes in between. Each update can add new pets, new eggs or a whole new biome. Right now the game has 265 pets, 148 eggs and 14 biomes.&lt;/p&gt;

&lt;p&gt;I run UpdateOtter, a small fan-made helper site for the game. This post is about the boring part that keeps it working: where the data lives and how it gets to the site.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;A game wiki like this has two kinds of content:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pages people read (guides, explanations).&lt;/li&gt;
&lt;li&gt;Tables people use (pets with their income, eggs with hatch times and spawn chances, mutations with multipliers).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The tables change every week. If I edited them by hand in a CMS admin panel, I would make mistakes, I would have no history, and I couldn't undo a bad update.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup: data as CSV files in git
&lt;/h2&gt;

&lt;p&gt;The site runs on WordPress with a custom theme. The game data is not typed into WordPress at all. It lives as plain CSV files inside the theme's git repository:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;pets.csv: name, rarity, base income, base weight, which egg it hatches from&lt;/li&gt;
&lt;li&gt;eggs.csv: name, rarity, biome, hatch time, spawn chance&lt;/li&gt;
&lt;li&gt;mutations.csv: name and income multiplier&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;When a change is merged into the main branch, the host deploys the theme automatically. After the deploy, an importer reads the CSV files and rebuilds the pet, egg and mutation pages. Every data file has a version number, which is printed on the pages, so a reader can see which data build they are looking at.&lt;/p&gt;

&lt;p&gt;What this gives me:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;History for free. Every change to a pet's income is a commit with a date.&lt;/li&gt;
&lt;li&gt;Easy rollback. A bad import is one revert away.&lt;/li&gt;
&lt;li&gt;Review before publish. A change goes through a pull request and automated checks before it is live.&lt;/li&gt;
&lt;li&gt;No admin-panel typos. Nobody edits numbers in a text box.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Telling readers how sure we are
&lt;/h2&gt;

&lt;p&gt;Most of the numbers come from the community wiki on Fandom, which is licensed CC BY-SA. I store facts, not copied text, and every page credits the wiki and keeps the same licence for our changes to the data.&lt;/p&gt;

&lt;p&gt;The site also tells readers how sure it is about each number:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Source: community wiki" on every row that comes from the wiki.&lt;/li&gt;
&lt;li&gt;"Not tested in game yet" or "Partly tested in game" on mechanics we haven't fully checked ourselves.&lt;/li&gt;
&lt;li&gt;A small "Do these numbers match your game? Yes / No" question on each pet page. When enough different players say yes over several days, the label changes to "Players confirm".&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This matters more than it sounds. Game wikis are often a few hours behind an update, and players notice wrong numbers fast. Being honest about the source keeps trust when a value turns out to be wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  The calculator math
&lt;/h2&gt;

&lt;p&gt;A pet's income per second is its base income times its mutation multiplier times a weight factor. The community wiki gives the weight rule: income grows with (weight / base weight) to the power 37/60, and more slowly (power 2/5) once a pet is more than 125 times its base weight.&lt;/p&gt;

&lt;p&gt;A simplified version of the main part, for pets under that 125x point, looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;income&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;baseIncome&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;mutationMultiplier&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;weight&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;baseWeight&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;ratio&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;weight&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="nx"&gt;baseWeight&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;baseIncome&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;mutationMultiplier&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;pow&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;ratio&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;37&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;60&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For example, a Phoenix has a base income of 85M Cash per second. With a Rainbow mutation (x3.5) at its base weight, that's about 297.5M per second. Our one in-game reading fits the weight rule so far, but we still need more readings to confirm the exact power, and the site says so.&lt;/p&gt;

&lt;p&gt;The calculator page also works without JavaScript. The server renders a correct example result, and JavaScript only makes the inputs live.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell anyone building a game wiki
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Keep the data in plain files, not in the CMS. CSV is boring and that's the point.&lt;/li&gt;
&lt;li&gt;Version your data and show the version on the page.&lt;/li&gt;
&lt;li&gt;Label your confidence honestly. "Not tested yet" is better than a confident wrong number.&lt;/li&gt;
&lt;li&gt;Credit your sources and respect their licence.&lt;/li&gt;
&lt;li&gt;Automate the deploy, so updating data is a commit and not a chore.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you play Steal an Egg, the calculator is here: &lt;a href="https://updateotter.com/steal-an-egg/calculator/" rel="noopener noreferrer"&gt;https://updateotter.com/steal-an-egg/calculator/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;UpdateOtter is a fan-made site and is not affiliated with Roblox or the game's developers.&lt;/p&gt;

&lt;p&gt;Note: I used an AI assistant to help write this post. I checked the facts and numbers against the live site.&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>webdev</category>
      <category>gamedev</category>
      <category>php</category>
    </item>
  </channel>
</rss>
