
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Chaos and Order</title>
      <link>https://www.youngju.dev/blog</link>
      <description>천천히 올바르게. AI Researcher &amp; DevOps Engineer Youngju&#39;s blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology.</description>
      <language>ko</language>
      <managingEditor>fjvbn2003@gmail.com (Youngju Kim)</managingEditor>
      <webMaster>fjvbn2003@gmail.com (Youngju Kim)</webMaster>
      <lastBuildDate>Fri, 14 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/capacity-planning/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-14-trend-gemini-3-7-flash-pricing-cadence.en</guid>
    <title>Gemini 3.7 Flash, Its Introductory Price and Its Three-Week Cadence — Why Model Cost Is a Conditional Value, Not a Fixed One</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-14-trend-gemini-3-7-flash-pricing-cadence.en</link>
    <description>What a practitioner should take from the Gemini 3.7 Flash announcement is not the size of the benchmark gains but two other things: an introductory price that doubles on a named date, and the fact that the previous model shipped three weeks earlier. Put together, model cost stops being a fixed line item and becomes a conditional value with an expiry date. This post works through what the published benchmarks compare and do not compare, and why the two numbers the announcement never discloses are exactly the ones that decide your architecture.</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>llm</category><category>cost-optimization</category><category>benchmark</category><category>api-design</category><category>capacity-planning</category><category>hacker-news</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-14-trend-gemini-3-7-flash-pricing-cadence.ja</guid>
    <title>Gemini 3.7 Flashの導入価格と3週間サイクル — モデル原価を固定費ではなく条件付きの値として扱う理由</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-14-trend-gemini-3-7-flash-pricing-cadence.ja</link>
    <description>Gemini 3.7 Flashの発表で実務者が見るべきはベンチマークの上げ幅ではなく、2つの事実です。1つは特定の日付で単価が2倍になる導入価格の構造、もう1つは直前のモデルが3週間前に出たという点です。2つが重なると、モデル原価は固定費ではなく期限付きの条件付きの値になります。公開されたベンチマークが何と比較し何と比較していないのか、そして発表で最後まで公開されなかった2つの数字がなぜアーキテクチャを決める数字なのかを整理します。</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>llm</category><category>cost-optimization</category><category>benchmark</category><category>api-design</category><category>capacity-planning</category><category>hacker-news</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/culture/2026-08-14-trend-gemini-3-7-flash-pricing-cadence</guid>
    <title>Gemini 3.7 Flash의 도입가와 3주 주기 — 모델 원가를 계약이 아니라 확률로 잡아야 하는 이유</title>
    <link>https://www.youngju.dev/blog/culture/2026-08-14-trend-gemini-3-7-flash-pricing-cadence</link>
    <description>Gemini 3.7 Flash 발표에서 실무자가 봐야 할 것은 벤치마크 상승폭이 아니라 두 가지입니다. 하나는 특정 날짜에 단가가 두 배로 오르는 도입가 구조이고, 다른 하나는 직전 모델이 3주 전에 나왔다는 사실입니다. 이 둘이 겹치면 모델 원가는 고정비가 아니라 만료일이 붙은 조건부 값이 됩니다. 공개된 벤치마크가 무엇을 비교하고 무엇을 비교하지 않는지, 그리고 발표에서 끝내 공개되지 않은 두 숫자가 왜 하필 아키텍처를 결정하는 숫자인지 정리합니다.</description>
    <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>llm</category><category>cost-optimization</category><category>benchmark</category><category>api-design</category><category>capacity-planning</category><category>hacker-news</category>
  </item>

    </channel>
  </rss>
