
  <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>Sat, 15 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.youngju.dev/tags/성능/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.en</guid>
    <title>A Complete Guide to Linux Performance Tools: How to Read the Numbers in the Output</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.en</link>
    <description>Interprets the numbers printed by top, vmstat, iostat, pidstat, sar and perf one column at a time. Covers which tool answers which question, which values create optical illusions, and the order in which to choose a tool using the USE method.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>성능</category><category>모니터링</category><category>운영</category><category>sysstat</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.ja</guid>
    <title>Linux性能ツール完全ガイド: 出力の数字を解釈する方法</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools.ja</link>
    <description>top、vmstat、iostat、pidstat、sar、perf が出力する数字を 1 列ずつ解釈します。どのツールがどの質問に答えるのか、どの値が錯覚を起こすのか、USE 方法論でツールを選ぶ順番までを整理しました。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>성능</category><category>모니터링</category><category>운영</category><category>sysstat</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools</guid>
    <title>리눅스 성능 도구 완전 가이드: 출력의 숫자를 해석하는 법</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-performance-tools</link>
    <description>top, vmstat, iostat, pidstat, sar, perf가 찍어 주는 숫자를 한 열씩 해석합니다. 어떤 도구가 어떤 질문에 답하는지, 어떤 값이 착시를 일으키는지, USE 방법론으로 도구를 고르는 순서까지 정리했습니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>성능</category><category>모니터링</category><category>운영</category><category>sysstat</category><category>명령어</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.en</guid>
    <title>The complete Linux troubleshooting command guide: from the first 60 seconds to root cause</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.en</link>
    <description>The diagnostic commands to run, in order, from the moment someone tells you a server is misbehaving. uptime, top, free, df, iostat, ss, journalctl — which number in each output to read, and what that number rules out versus what it leaves standing.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>트러블슈팅</category><category>운영</category><category>장애대응</category><category>명령어</category><category>성능</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.ja</guid>
    <title>Linux障害対応コマンド完全ガイド: 最初の60秒から根本原因まで</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands.ja</link>
    <description>サーバーの様子がおかしいと連絡を受けた瞬間から順番に実行する診断コマンドを整理します。uptime、top、free、df、iostat、ss、journalctlまで、各出力のどの数字を見るべきか、その数字が何を除外して何を残すのかを説明します。</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>트러블슈팅</category><category>운영</category><category>장애대응</category><category>명령어</category><category>성능</category>
  </item>

  <item>
    <guid>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands</guid>
    <title>리눅스 장애 대응 명령어 완전 가이드: 첫 60초부터 근본 원인까지</title>
    <link>https://www.youngju.dev/blog/linux/2026-08-15-guide-linux-troubleshooting-commands</link>
    <description>서버가 이상하다는 연락을 받은 순간부터 순서대로 실행하는 진단 명령어를 정리합니다. uptime, top, free, df, iostat, ss, journalctl까지 각 출력의 어느 숫자를 봐야 하는지, 그 숫자가 무엇을 배제하고 무엇을 남기는지 설명합니다.</description>
    <pubDate>Sat, 15 Aug 2026 00:00:00 GMT</pubDate>
    <author>fjvbn2003@gmail.com (Youngju Kim)</author>
    <category>리눅스</category><category>트러블슈팅</category><category>운영</category><category>장애대응</category><category>명령어</category><category>성능</category>
  </item>

    </channel>
  </rss>
