<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cost on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/categories/cost/</link>
    <description>Recent content in Cost on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Apr 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/categories/cost/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>More CPUs or Newer CPUs</title>
      <link>https://ronaldbradford.com/blog/more-cpus-or-newer-cpus-2025-04-02/</link>
      <pubDate>Wed, 02 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/more-cpus-or-newer-cpus-2025-04-02/</guid>
      <description>In a CPU-bound database workload, regardless of price, would you scale-up or scale-new?&#xA;What if price was the driving factor, would you scale-up or scale-new?&#xA;I am using as a baseline the first available AWS Graviton2 processor for RDS (r6g).</description>
    </item>
  </channel>
</rss>
