---
title: "Performance"
description: "817 posts about Performance, summarised, each linking to the original."
---

# Performance
> 817 posts about Performance, summarised, each linking to the original.

## Articles

### [Inside NVIDIA Rubin GPU Architecture: Powering the Era of Agentic AI](https://yomu.fyi/post/inside-nvidia-rubin-gpu-architecture-powering-the-era-of-agentic-ai.md)
- Company: [NVIDIA](https://yomu.fyi/company/nvidia-developer-blog.md)
- Author: Eduardo Alvarez
- Published: Jul 21, 2026
- Type: Explainer

Agentic artificial intelligence workloads require sustained multistep inference, demanding low per-step latency, high decode throughput, and efficient long-context processing. NVIDIA designed the Rubin GPU to deliver up to ten times more agentic throughput per unit of energy than Blackwell. The hardware combines 336 billion transistors across two dies unified by NV-HBI, up to 288 GB of HBM4 memory providing 22 TB/s peak bandwidth, and the third-generation Transformer Engine reaching up to 50 petaflops of NVFP4 compute. Performance optimizations include inline descriptor updates for the Tensor Memory Accelerator, doubled K-dimension instruction throughput, 3-bit lookup-table weights, and structured 2:4 sparse attention compression. At the rack level, Vera Rubin NVL72 leverages Intelligent Power Smoothing and DSX MaxLPS to enable up to 40% more GPUs within a fixed power budget.


### [NVIDIA Vera CPU: Olympus Cores Built for Maximum Single-Thread Performance in Agentic AI](https://yomu.fyi/post/nvidia-vera-cpu-olympus-cores-built-for-maximum-single-thread-performa.md)
- Company: [NVIDIA](https://yomu.fyi/company/nvidia-developer-blog.md)
- Author: Praveen Menon
- Published: Jul 21, 2026
- Type: Explainer

Agentic AI workloads shift critical execution paths onto CPUs through sandboxed environments that execute code, invoke tools, and manage runtime states. The NVIDIA Vera CPU addresses these compute requirements via Olympus cores built to maximize single-thread performance and instructions per cycle under full socket load. To handle irregular control flows and pointer-heavy structures, Olympus combines a ten-wide decode engine, neural branch prediction supporting two taken branches per cycle, dependency-breaking acceleration, and dedicated graph prefetchers. Across scale-up systems, dual-socket Vera configurations leverage second-generation NVLink-C2C interconnects to maintain a clean two-NUMA-node topology alongside PCIe 6.4, CXL 3.1, and Arm CCA confidential computing. These architectural choices provide predictable latency and memory bandwidth across highly concurrent reinforcement learning and agent loops.


### [Personalizing Airbnb search by learning from the guest journey](https://yomu.fyi/post/personalizing-airbnb-search-by-learning-from-the-guest-journey.md)
- Company: [Airbnb](https://yomu.fyi/company/airbnb.md)
- Author: Daochen Zha
- Published: Jul 21, 2026

Airbnb replaced hundreds of hand-crafted ranking features with a Transformer-based sequence model that captures both long-term booking history and short-term browsing behavior. To keep latency low and throughput high, sequence representations are generated via daily batch jobs and combined with real-time queries using a co-trained setwise ranker.


### [Supabase Pipelines is now in Public Alpha](https://yomu.fyi/post/supabase-pipelines-is-now-in-public-alpha.md)
- Company: [Supabase](https://yomu.fyi/company/supabase.md)
- Author: riccardo\_busetti
- Published: Jul 21, 2026
- Type: Announcement

Supabase Pipelines has moved into public alpha as a service for replicating Supabase Postgres data to external analytical systems in near real time. The release adds automatic application of supported schema changes, faster initial synchronization through parallelism, and a destination request form for ClickHouse, Snowflake, and DuckLake; Google BigQuery is the first destination available to everyone in public alpha. Powered by the open-source Rust-based Supabase ETL, Pipelines uses Postgres logical replication to copy existing tables, stream inserts, updates, deletes, and truncates, and resume from the last acknowledged position after interruptions. It provides at-least-once delivery and managed pipeline controls, while remaining an alpha product with ongoing work on throughput, batching, backpressure, broader schema support, and additional destinations.


### [Scaling document classification to 100k+ labels](https://yomu.fyi/post/scaling-document-classification-to-100k-labels.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Jane Zhang, Arnav Singhvi
- Published: Jul 20, 2026
- Type: Benchmark

Large-taxonomy classification must map freeform text to 35,000–100,000 labels while meeting quality, cost, and throughput requirements. The benchmark compares vector search, a two-step vector-search-plus-AI-Classify workflow, and direct frontier-model calls across transaction, company, and biomedical datasets, using hybrid semantic and BM25 retrieval with Reciprocal Rank Fusion for the search stages. The combined workflow performed best, reaching 0.81 average accuracy versus 0.76 for Gemini 3.5 Flash, while costing roughly one-hundredth as much per document; its strongest average setting shortlisted the top 20 labels. Vector search alone was nearly 100 times cheaper than the workflow but scored more than 20 points lower, while full-taxonomy frontier calls could exceed context limits. Taxonomy updates can be handled by embedding and ingesting changed labels rather than retraining or redeploying classifiers.


### [Content Ingestion & Podcast Video Incident Report](https://yomu.fyi/post/content-ingestion-podcast-video-incident-report.md)
- Company: [Spotify](https://yomu.fyi/company/spotify.md)
- Author: Spotify Engineering
- Published: Jul 20, 2026
- Type: Incident / postmortem

On June 24, video transcoding infrastructure reached maximum capacity, causing hours of publishing delays for Spotify video podcast episodes. Four converging factors drove the disruption: insufficient headroom for content spikes, an active routine batch processing job, higher compute costs from a recent video quality upgrade, and a scheduling bug reducing hardware throughput by roughly 10%. Creators exacerbated the backlog by re-uploading unconfirmed episodes, while four hours elapsed between the earliest alerts and formal incident response. Engineers halted the batch job, patched the scheduling defect, and brought an extra compute cluster online to clear all backlogs overnight. Spotify subsequently increased transcoding capacity by approximately 67% and initiated cross-team investments in workload prioritization, rate limiting, and earlier capacity alerting.


### [NVIDIA NVLink: The Scale-Up Network for AI Factories](https://yomu.fyi/post/nvidia-nvlink-the-scale-up-network-for-ai-factories.md)
- Company: [NVIDIA](https://yomu.fyi/company/nvidia-developer-blog.md)
- Author: Elizabeth Goodman
- Published: Jul 20, 2026
- Type: Announcement

Scale-up networking has emerged as a critical architectural component for AI factories supporting trillion-parameter models, mixture-of-experts architectures, and disaggregated serving. NVIDIA presents its sixth-generation NVLink scale-up fabric and NVLink 6 Switch to address latency-sensitive all-to-all GPU communication and offload collective operations. In simulation benchmarks on models like DeepSeek-R1, Qwen 235B, and a simulated 2T parameter model, NVLink achieved up to 2.3X higher decode throughput than off-the-shelf Ethernet in a 72-accelerator domain. The architecture integrates NVLink-C2C to supply 1.8 TB/s of coherent CPU-GPU bandwidth in the Vera Rubin NVL72 platform, as well as NVLink Fusion for integrating semi-custom silicon XPUs. Through co-designed hardware, SHARP in-network compute, and NCCL libraries, the platform optimizes token throughput, factory uptime, and deployment economics.


### [MongoDB Query Tracing in .NET with Sentry + OTLP](https://yomu.fyi/post/mongodb-query-tracing-in-net-with-sentry-otlp.md)
- Company: [Sentry](https://yomu.fyi/company/sentry.md)
- Author: James Crosswell
- Published: Jul 20, 2026
- Type: Tutorial

Measuring MongoDB performance in a .NET application requires command details, durations, and enough context to distinguish isolated spikes from recurring query patterns. The post presents an end-to-end setup that uses MongoDB’s built-in OpenTelemetry Activity instrumentation, the .NET OpenTelemetry SDK, Sentry.OpenTelemetry.Exporter, and OTLP ingestion rather than a dedicated Sentry.MongoDB integration. Configuration initializes Sentry with UseOtlp(), subscribes to MongoTelemetry.ActivitySourceName, adds MongoDB instrumentation, and exports spans with AddSentryOtlp(...), while avoiding duplicate spans from overlapping hooks. Query context appears in Sentry traces, span samples, and the Queries experience, with Relay generating parameterized values for aggregation but retaining raw db.query.text per span. The post also demonstrates client-side redaction and describes server-side scrubbing, while exporter propagation bridges preserve correlation with errors and replays.


### [In-House LLM Serving at Netflix](https://yomu.fyi/post/in-house-llm-serving-at-netflix.md)
- Company: [Netflix](https://yomu.fyi/company/netflix.md)
- Author: Netflix Technology Blog
- Published: Jul 17, 2026
- Type: Problem & solution

Netflix established an in-house serving platform to run large language model inference directly inside existing production environments alongside traditional machine learning models. Built upon NVIDIA Triton Inference Server and vLLM, the unified architecture handles member-scale routing, candidate generation, feature fetching, and model execution over gRPC and OpenAI-compatible HTTP endpoints. The team shifted their primary engine from TensorRT-LLM to vLLM to support custom architectures, simpler debugging, and non-trivial constraint logic. Addressing production obstacles required patching Triton's frontend for guided decoding, pinning dependent library versions, rewriting logits processors in C++ for vLLM V1, and handling state machine resets during engine preemptions. The resulting platform unifies deployment flows while preserving operational stability across evolving model schemas.


### [Eclipse Dataspace Components on AWS: Cost optimization strategies](https://yomu.fyi/post/eclipse-dataspace-components-on-aws-cost-optimization-strategies.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Jorge Hernández Suárez
- Published: Jul 17, 2026
- Type: Explainer

Deploying Eclipse Dataspace Components (EDC) connectors on AWS presents challenges in forecasting infrastructure expenses without clear benchmarks. Estimated costs differ substantially between business-critical setups and non-critical environments based on compute and database sizing. A business-critical configuration relying on Amazon Aurora PostgreSQL db.r6g.large and standard Amazon ECS with AWS Fargate totals an estimated 387.00 USD monthly in the eu-south-2 region. Sizing down to db.t4g.medium and switching to AWS Fargate Spot lowers the non-critical monthly expense to 164.00 USD, representing a 58% reduction. Core cost drivers remain baseline infrastructure components, while storage, API calls, and data transfers contribute marginally under baseline assumptions.


### [Q&A: How Capcom Brought Path Tracing to RE ENGINE Across PRAGMATA and Resident Evil Requiem](https://yomu.fyi/post/q-a-how-capcom-brought-path-tracing-to-re-engine-across-pragmata-and-r.md)
- Company: [NVIDIA](https://yomu.fyi/company/nvidia-developer-blog.md)
- Author: Michelle Horton
- Published: Jul 16, 2026
- Type: Explainer

Capcom integrated path tracing into RE ENGINE across PRAGMATA and Resident Evil Requiem to deliver unified indirect and direct lighting. Over two years, the team built a reference path tracer validated against standard DCC tools, scaling it down into a real-time version optimized for NVIDIA DLSS Ray Reconstruction denoising. To manage rendering performance, Capcom avoided expensive AlphaTest texture lookups by creating a ScreenSpaceAlphaTest method comparing ray-hit positions against screen-space depth. Sampling noise in emissive and indoor regions is mitigated using Next Event Estimation and a custom implementation of ReSTIR GI. Replacing traditional shadow maps with continuous path tracing reduced the visual gap between gameplay and cinematics while enabling real-time light transmission through strand hair.


### [What happens in the milliseconds after you tap pay](https://yomu.fyi/post/what-happens-in-the-milliseconds-after-you-tap-pay.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Harsha Pasala, Subhadip Chanda
- Published: Jul 16, 2026
- Type: Tutorial

At checkout, fraud scoring must combine transaction inference with customer-specific rules while keeping latency low enough for an interactive payment. The retail-app sample pairs a FastAPI backend and React frontend in a Databricks App with Model Serving route optimization and Lakebase Postgres, where the model retrieves historical features and the backend reads profile controls. A transaction is scored first, then checked against daily spending, international-transaction, and country rules; pooled OAuth-authenticated connections and token-rotation handling avoid repeated handshakes and stale credentials. In the supplied benchmark, route-optimized calls reached 27.2 ms p50 and 37.3 ms p95 end-to-end, with feature lookup at 8.9 ms p50, CatBoost inference at 0.4 ms, and network overhead at 17.4 ms p50; actual performance varies by model.


### [Scaling Agentic AI Factories Through Extreme Co-Design with NVIDIA BlueField](https://yomu.fyi/post/scaling-agentic-ai-factories-through-extreme-co-design-with-nvidia-blu.md)
- Company: [NVIDIA](https://yomu.fyi/company/nvidia-developer-blog.md)
- Author: Michelle Horton
- Published: Jul 16, 2026
- Type: Explainer

Agentic artificial intelligence workflows transform data center infrastructure by turning context management, security enforcement, and inter-service communication into active components of the inference data path. To prevent host central processing units and graphics processing units from stalling on these tasks, NVIDIA introduces BlueField-4 data processing units, Vera BlueField-4 STX storage processors, and the DOCA software platform. The BlueField-4 processor offloads Layer 3 routing, encryption, and telemetry using a sixty-four-core Grace processor with up to eight hundred gigabits per second connectivity. Simultaneously, the Vera BlueField-4 STX powers the NVIDIA CMX context memory platform alongside DOCA Memos to store, protect, and share key-value cache across flash storage tiers. This co-designed infrastructure isolates tenant traffic and accelerates context reuse without degrading host-side agent execution.


### [How Unity Catalog managed tables bring interoperability, performance, and unified governance to the Lakehouse](https://yomu.fyi/post/how-unity-catalog-managed-tables-bring-interoperability-performance-an.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Alex Jiang, Tathagata “TD” Das
- Published: Jul 16, 2026
- Type: Announcement

Unity Catalog external access to Unity Catalog managed Delta tables is now in Public Preview, allowing external engines to create, read, and write while governance remains centralized. The announcement addresses the previous multi-engine trade-off: external tables enabled access but lacked managed-table performance optimizations and governance guarantees. Catalog commits coordinate writes through Unity Catalog, making it the source of truth for table state and enabling safe external writes, multi-statement transactions, and auditing of external operations. Predictive Optimization cleans storage, collects query statistics, and selects Liquid clustering columns as query patterns change; the post says these capabilities can deliver up to 50% storage cost savings and 20x faster queries. Support includes Spark, Flink, Starburst, DuckDB, and StreamNative, with open APIs and Delta Kernel extending integrations across Databricks UC and UC OSS.


### [Newer Models, Same Advantage](https://yomu.fyi/post/newer-models-same-advantage.md)
- Company: [Hugging Face](https://yomu.fyi/company/hugging-face.md)
- Author: Erick Lachmann, Gabriel Pimenta de Freitas Cardoso, Francisco de Almeida Rocha Alves, Victor Gabriel Ferreira Barbosa
- Published: Jul 16, 2026
- Type: Benchmark

DharmaOCR, a Brazilian Portuguese-focused OCR model, is evaluated against newer Mistral OCR4 and Unlimited-OCR systems on a Portuguese-only benchmark. The article attributes its performance to a two-stage training pipeline: supervised fine-tuning on varied Portuguese documents, followed by Direct Preference Optimization (DPO) using comparative output preferences. Fine-tuning concentrates model capacity on Brazilian Portuguese vocabulary, syntax, and document structures, while DPO targets repetitive or incoherent generation, reducing inference time and cost and improving stability according to the article. DharmaOCR scored 0.925, compared with 0.798 for Mistral OCR4 and 0.7587 for Unlimited-OCR, while examples from handwritten ENEM essays show the competitors misreading Brazilian names and phrases that DharmaOCR handled correctly. The conclusion is that newer architectures can raise absolute performance, but directing finite resources at one domain can preserve a measurable specialist advantage.


### [Scaling to 1 million concurrent sandboxes in seconds](https://yomu.fyi/post/scaling-to-1-million-concurrent-sandboxes-in-seconds.md)
- Company: [Modal](https://yomu.fyi/company/modal.md)
- Published: Jul 16, 2026
- Type: Problem & solution

Modal rebuilt its sandbox platform to support millions of concurrent sandboxes and tens of thousands of creations per second, removing all central bottlenecks from the control plane. The new architecture eliminates central coordination and durable datastores from the critical path, using horizontally scaled scheduling servers that run a fast load-balancing algorithm against in-memory cached worker state from Redis streams. Workers are contacted directly via RPC to create sandboxes, and sandbox metadata is written asynchronously, avoiding O(sandboxes) and O(nodes) operations that limited previous systems. In a benchmark, Modal created 1 million sandboxes in under a minute with median time-to-interactivity under half a second, though the long tail is attributed to kernel and network contention like the rtnl lock. The system is designed to scale without practical limits, supporting use cases like reinforcement learning and background agents that require massive concurrent sandbox creation.


### [Upgrading Checkout Blocks app to Polaris web components](https://yomu.fyi/post/upgrading-checkout-blocks-app-to-polaris-web-components.md)
- Company: [Shopify](https://yomu.fyi/company/shopify.md)
- Author: 2023-10-18
- Published: Jul 16, 2026
- Type: Problem & solution

Checkout Blocks upgraded all five UI extensions from React and Shopify’s legacy Remote UI bridge to remote-dom with Preact and Polaris web components, while moving from JavaScript to TypeScript and API version 2026-01. The migration addressed checkout’s performance sensitivity and Shopify’s requirement that deployments move off versions earlier than 2026-01. A parallel core-next library allowed extensions to transition incrementally, with shared providers, telemetry, hooks, helpers, and rules adapted before legacy core was removed. To meet the remote-dom CLI’s 64KB gzip limit, the team dropped react-reconciler, replaced liquidjs with a smaller parser validated against more than 42,000 lines of merchant configurations, replaced dayjs, and retained markdown-to-jsx through Preact compatibility. Transferred bundles fell 40% to 85%, while weighted ELT improved 8% at P50 and 7% at P90.


### [July 2026 newsletter](https://yomu.fyi/post/july-2026-newsletter.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Jul 16, 2026
- Type: Announcement

The July 2026 newsletter rounds up ClickHouse releases, community projects, benchmarks, engineering work, and upcoming events in real-time data warehousing. Version 26.6 adds hypothetical skip indexes, cascading refreshable materialized-view dependencies, experimental continuous queries, AI embedding functions, PNG output, CLI documentation, and geospatial improvements. A CostBench comparison running the full analytics path over 28 hours found better cost-performance for ClickHouse Cloud than Snowflake Interactive Tables, which required a continuously running refresh warehouse for pre-aggregated data. Other features cover conversational analytics with ClickHouse Cloud, LibreChat, and MCP; Postgres change-data capture through Debezium and Kafka; local agent queries with chDB; high-concurrency tuning; and Silk, whose fiber runtime targets lower I/O tail latency. Quick reads report ingestion, caching, security, and multi-tenant SQL developments.


### [How Stripe uses graph search and state machines to auto-remediate a global database fleet](https://yomu.fyi/post/how-stripe-uses-graph-search-and-state-machines-to-auto-remediate-a-gl.md)
- Company: [Stripe](https://yomu.fyi/company/stripe.md)
- Author: Pragya Mehta
- Published: Jul 16, 2026
- Type: Problem & solution

Stripe describes how its Document Database fleet previously handled degraded MongoDB shards with single-step, hard-coded plugins that struggled with combined failures, intermediate states, and more than 40 shard layouts. The replacement models shard topology and health as a directed graph, with infrastructure operations as edges and safety invariants defining valid states. A simulator uses breadth-first search to find minimum-operation recovery paths, while an abstraction over Temporal contexts lets the same remediation logic run in memory without real infrastructure calls; later, the system also uses Dijkstra's algorithm. The system reduced pager volume by 30%—about 200 pages annually—reclaimed 12 days of fleet health each year, and handled a new layout with zero code changes, according to the post.


### [Why Trainy migrated from Amazon RDS Postgres to ClickHouse Managed Postgres](https://yomu.fyi/post/why-trainy-migrated-from-amazon-rds-postgres-to-clickhouse-managed-pos.md)
- Company: [Clickhouse](https://yomu.fyi/company/clickhouse.md)
- Published: Jul 15, 2026
- Type: Problem & solution

Trainy’s Pluto is an open-source experiment tracker that separates analytics metrics in ClickHouse Cloud from relational run metadata in Postgres. Its original metadata store, Amazon RDS Postgres, was too expensive for the volume observed and contributed to slower initial page loads, so Trainy migrated roughly 40–50 GB to ClickHouse Managed Postgres, which uses local NVMe storage and keeps both databases in one account. After migration, initial page loads became 2–3 times faster, while a complex query reported as taking 10–15 minutes previously returned in five seconds; visualization queries over runs with hundreds of thousands of steps typically return in 50–100 milliseconds at the P50. Trainy reports 100% reliable ingestion with zero dropped data points and says the unified stack could support future joins between GPU metrics and run metadata, as well as governed agent access.


[Newer posts](https://yomu.fyi/topic/performance/page/10.md) · [Older posts](https://yomu.fyi/topic/performance/page/12.md)