<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Performance</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Performance feed</description>
    <item>
      <title>Microsoft Commits Maia to Multi-Gigawatt Inference, and its Efficiency Metric Draws Questions</title>
      <link>https://www.infoq.com/news/2026/10/azure-maia-300/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/10/azure-maia-300/en/headerimage/generatedHeaderImage-1791943943820.jpg"/&gt;&lt;p&gt;Microsoft will scale its Maia accelerator family to multi-gigawatt deployments from 2027, making it the primary inference system for its own products. Maia 300 collapses scale-up and scale-out onto one Ethernet fabric and moves KV state between prefill and decode workers without leaving it. Practitioners have questioned the tokens-per-watt claim that leads the announcement.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Hardware</category>
      <category>Cloud</category>
      <category>Performance</category>
      <category>Architecture</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>news</category>
      <pubDate>Fri, 16 Oct 2026 06:02:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/10/azure-maia-300/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-10-16T06:02:00Z</dc:date>
      <dc:identifier>/news/2026/10/azure-maia-300/en</dc:identifier>
    </item>
    <item>
      <title>Instagram Modernized its UI with an AI-Native Architecture, Cutting Token Costs by 33%</title>
      <link>https://www.infoq.com/news/2026/10/instagram-compose-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/10/instagram-compose-migration/en/headerimage/aws-reliability-dns-1792077775251.jpg"/&gt;&lt;p&gt;Instagram Direct migrated its Android UI from the legacy Android View system to Jetpack Compose, creating an AI-native UI codebase that is easier for AI coding agents to understand, modify, and maintain. According to Instagram engineers, the migration reduced UI code volume by 50% and token costs per AI agent session by 33%.&lt;/p&gt; &lt;i&gt;By Sergio De Simone&lt;/i&gt;</description>
      <category>Jetpack Compose</category>
      <category>Mobile</category>
      <category>Performance</category>
      <category>Facebook</category>
      <category>AI coding agents</category>
      <category>Android</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 15 Oct 2026 16:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/10/instagram-compose-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</guid>
      <dc:creator>Sergio De Simone</dc:creator>
      <dc:date>2026-10-15T16:00:00Z</dc:date>
      <dc:identifier>/news/2026/10/instagram-compose-migration/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: How Eve Online Leverages Head Based Sampling to Observe "Fun"</title>
      <link>https://www.infoq.com/presentations/eve-observability-head-sampling/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</link>
      <description>&lt;img src="https://res.infoq.com/presentations/eve-observability-head-sampling/en/mediumimage/nicholas-herring-medium-1791444748399.jpg"/&gt;&lt;p&gt;Nicholas Herring shares how EVE Online tackles distributed tracing and observability across a 20-year-old MMO architecture. He discusses leveraging head-based, dynamic exponential moving average (EMA), and deterministic sampling techniques to maintain high system fidelity, control telemetry costs, and avoid performance degradation under high-throughput real-time game simulations.&lt;/p&gt; &lt;i&gt;By Nicholas Herring&lt;/i&gt;</description>
      <category>Observability</category>
      <category>Real Time</category>
      <category>Distributed Systems</category>
      <category>Transcripts</category>
      <category>Distributed Tracing</category>
      <category>QCon London 2026</category>
      <category>Telemetry</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>DevOps</category>
      <category>presentation</category>
      <pubDate>Tue, 13 Oct 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/eve-observability-head-sampling/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</guid>
      <dc:creator>Nicholas Herring</dc:creator>
      <dc:date>2026-10-13T11:00:00Z</dc:date>
      <dc:identifier>/presentations/eve-observability-head-sampling/en</dc:identifier>
    </item>
    <item>
      <title>Article: When Should You Use Liquid Clustering? Benchmarking Lakehouse Layout Strategies</title>
      <link>https://www.infoq.com/articles/liquid-clustering-lakehouse-layout/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</link>
      <description>&lt;img src="https://res.infoq.com/articles/liquid-clustering-lakehouse-layout/en/headerimage/liquid-clustering-lakehouse-layout-header-1791465984987.jpg"/&gt;&lt;p&gt;Physical data layout is one of the most consequential decisions in lakehouse engineering. The author compares Liquid Clustering, ZOrdering, and partitioning across four workload types on Delta Lake, uncovering two undocumented failure modes that likely affect production systems today and offering a decision framework for choosing the right layout strategy.&lt;/p&gt; &lt;i&gt;By Kushal Kumar Vishwakarma&lt;/i&gt;</description>
      <category>Performance Evaluation</category>
      <category>Query</category>
      <category>Data Storage</category>
      <category>Benchmark</category>
      <category>Clustering &amp; Caching</category>
      <category>Data Lake</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Mon, 12 Oct 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/liquid-clustering-lakehouse-layout/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</guid>
      <dc:creator>Kushal Kumar Vishwakarma</dc:creator>
      <dc:date>2026-10-12T11:00:00Z</dc:date>
      <dc:identifier>/articles/liquid-clustering-lakehouse-layout/en</dc:identifier>
    </item>
    <item>
      <title>Github Migrates Copilot Runtime to Rust with AI-Assisted Rewrite</title>
      <link>https://www.infoq.com/news/2026/10/github-copilot-rust-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;GitHub migrated more than 800,000 lines of Copilot runtime code from TypeScript and Node.js to Rust in about 14.5 weeks using AI-assisted development. The incremental migration used N-API interoperability, automated testing, human review, and 128 pull requests while continuing to ship releases.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Rust</category>
      <category>migration</category>
      <category>TypeScript</category>
      <category>AI Assisted Coding</category>
      <category>AI coding agents</category>
      <category>Node.js</category>
      <category>Automated testing</category>
      <category>SDK</category>
      <category>Performance</category>
      <category>copilot</category>
      <category>Rewrite</category>
      <category>github</category>
      <category>CLI</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Fri, 09 Oct 2026 14:29:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/10/github-copilot-rust-migration/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-10-09T14:29:00Z</dc:date>
      <dc:identifier>/news/2026/10/github-copilot-rust-migration/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Ontology‐Driven Observability: Building the E2E Knowledge Graph at Netflix Scale</title>
      <link>https://www.infoq.com/presentations/netflix-observability-aiops-ontology-scale/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</link>
      <description>&lt;img src="https://res.infoq.com/presentations/netflix-observability-aiops-ontology-scale/en/mediumimage/medium-1790845339712.jpg"/&gt;&lt;p&gt;Prasanna Vijayanathan and Renzo Sanchez-Silva share how Netflix tackles observability across 38M events/sec. They discuss replacing reactive monitoring with an AI-driven operational ontology and agentic workflows using Claude and graph databases. They explain how unifying MELT telemetry into queryable knowledge graphs enables automated triaging, root-cause analysis, and self-healing systems.&lt;/p&gt; &lt;i&gt;By Prasanna Vijayanathan, Renzo Sanchez-Silva&lt;/i&gt;</description>
      <category>AIOps</category>
      <category>Site Reliability Engineering</category>
      <category>Observability</category>
      <category>Architecture</category>
      <category>Transcripts</category>
      <category>QCon London 2026</category>
      <category>Ontology</category>
      <category>Telemetry</category>
      <category>Scaling</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>presentation</category>
      <pubDate>Fri, 09 Oct 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/netflix-observability-aiops-ontology-scale/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Performance</guid>
      <dc:creator>Prasanna Vijayanathan, Renzo Sanchez-Silva</dc:creator>
      <dc:date>2026-10-09T11:00:00Z</dc:date>
      <dc:identifier>/presentations/netflix-observability-aiops-ontology-scale/en</dc:identifier>
    </item>
  </channel>
</rss>
