<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>성능 가이드 on Meshs One Blog</title>
    <link>https://blog.meshs.one/tags/%EC%84%B1%EB%8A%A5-%EA%B0%80%EC%9D%B4%EB%93%9C/</link>
    <description>Recent content in 성능 가이드 on Meshs One Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 07 Jul 2026 08:00:00 +0800</lastBuildDate>
    <atom:link href="https://blog.meshs.one/tags/%EC%84%B1%EB%8A%A5-%EA%B0%80%EC%9D%B4%EB%93%9C/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>프롬프트 캐싱 &#43; 스마트 라우팅: LLM 비용 70% 절감을 위한 개발자 가이드</title>
      <link>https://blog.meshs.one/ko/posts/prompt-caching-smart-routing-developer-guide/</link>
      <pubDate>Tue, 07 Jul 2026 08:00:00 +0800</pubDate>
      <guid>https://blog.meshs.one/ko/posts/prompt-caching-smart-routing-developer-guide/</guid>
      <description>We need to translate the given English text into Korean following the specified localization style. The text is: &amp;#34;How prompt caching and model routing work together to deliver 70%&#43; cost savings — with real numbers, configuration examples, and a confidence threshold strategy you can implement today.&amp;#34; Key points: Use Korean tech industry terminology, Korean-English mixed notation, adapt to SOV order, numbers in Korean format (70%&#43; -&amp;gt; 70%&#43;? Actually 70%&#43; is fine, but maybe &amp;#34;70% 이상&amp;#34;? But the style says numbers use Korean format like 10,000→1만, but percentage might stay. Also &amp;#34;70%&#43;&amp;#34; can be &amp;#34;70% 이상&amp;#34;. But careful: &amp;#34;70%&#43; cost savings&amp;#34; -&amp;gt; &amp;#34;비용 절감 70% 이상&amp;#34;. Also &amp;#34;prompt caching&amp;#34; and &amp;#34;model routing&amp;#34; are technical terms, keep as is or mixed? Style says use Korean-English mixed notation: API, AI, etc. So &amp;#34;프롬프트 캐싱(prompt caching)&amp;#34; or just &amp;#34;프롬프트 캐싱&amp;#34;? Probably keep English in parentheses or just as is? The style reference is NAVER D2, Medium Korea tech blogs. They often use English terms directly. So &amp;#34;프롬프트 캐싱&amp;#34; and &amp;#34;모델 라우팅&amp;#34; are common. But to be safe, use mixed: &amp;#34;프롬프트 캐싱(Prompt Caching)&amp;#34;? However the instruction says &amp;#34;Use Korean-English mixed notation (API, AI, etc.)&amp;#34; meaning terms like API are kept as API. So for &amp;#34;prompt caching&amp;#34; it&amp;#39;s a phrase, likely keep as &amp;#34;프롬프트 캐싱&amp;#34; or &amp;#34;Prompt Caching&amp;#34;? I think &amp;#34;프롬프트 캐싱&amp;#34; is fine. Similarly &amp;#34;모델 라우팅&amp;#34;. Also &amp;#34;confidence threshold strategy&amp;#34; -&amp;gt; &amp;#34;신뢰도 임계값 전략&amp;#34; or &amp;#34;confidence threshold 전략&amp;#34;? Use mixed: &amp;#34;confidence threshold 전략&amp;#34;. Sentence structure: Adapt to Korean SOV. Original is a headline-like phrase. Translation should be a natural Korean sentence. Possibly: &amp;#34;프롬프트 캐싱과 모델 라우팅이 어떻게 함께 작동하여 70% 이상의 비용 절감을 제공하는지 — 실제 수치, 구성 예제, 그리고 오늘 바로 구현할 수 있는 confidence threshold 전</description>
    </item>
  </channel>
</rss>
