benchmark 47
- Go PGO in Practice: What go build -pgo Changed in a Log Router, Measured
- Replay Data vs Catastrophic Forgetting, Measured: Mixing General Text into a Fine-Tune
- AI SDLC: The Agent-Written Code Review Loop, Measured - Review, Fix, Re-review on 14 Go PRs
- Enterprise AI: Token Budgets That Hold Under Concurrency - Measured on an LLM Gateway
- AI SDLC: Spec to PR With Coding Agents, Measured - What to Gate Before and After the Agent
- Tokio Performance Pitfalls, Measured: Blocking, Mutexes, Spawns and File I/O
- AI Code Review Gates in CI, Measured: 26 Seeded Agent Defects Against a Go Pipeline
- Rust Error Handling: thiserror vs anyhow, Measured on One Parser
- Fine-Tuning Evaluation, Measured: Held-Out Perplexity, KL Drift and Benchmarks
- AI Security: Hidden Prompt Injection vs Agent Page Readers, Measured
- Rust Profiling Practical Guide: sample, Flame Graphs and a Counting Allocator, Measured
- AI Security: Secrets in Agent Logs, Measured - What gitleaks and Redaction Actually Catch
- Continuous batching, measured: llama.cpp static vs continuous scheduling on one M2 Pro
- Go pprof alloc_space: 2.87 GB of garbage from one `+=` in a loop
- Rust RwLock on a Read-Heavy Path: parking_lot vs std::sync, Measured
- Rust Release Profiles in Production: LTO, codegen-units, and target-cpu Cut Our p99 by 54%
- GOGC=off with runtime.SetMemoryLimit: the GC tuning pair that cut our p99 61%
- Go sync.Pool and String Interning: Beating GC Pressure in the Same Tokenizer Sidecar
- Rust Small-String Optimization: compact_str Cut Our LLM Tokenizer Sidecar's p99 by 67%
- sync.Pool vs fresh allocation, round two: p99 under a live HTTP handler
- Rust Allocators in a Hot Parsing Loop: mimalloc vs glibc malloc, Measured
- Time-to-First-Token for Streamed LLM Responses: .NET 9 vs Node 22, Measured
- Rust Ownership for .NET Developers: C# vs Rust Memory Behaviour on the Same Pipeline
- Embedding Call Throughput in .NET 9, Python and Go: Batch Sizes 1 to 256, Measured
- .NET 9 vs Node 22 as an LLM API Gateway: Requests per Second, p99 Latency and Memory, Measured
- TypeScript vs Go vs Rust for LLM Tooling: One MCP Server, Three Languages, Measured
- Go vs Rust for a GC-Sensitive AI Inference Gateway: p99 Latency, Memory and GC Pauses, Measured
- Rust vs Go for a CPU-Bound Microservice: Throughput, Tail Latency, Memory and Deploy Friction, Measured
- Rust vs Python for an AI Inference Microservice: 1.5x Throughput, 3x Less Memory, 3x Better p99
- Java vs Kotlin for a Spring Boot Microservice: Same Runtime, 40% Less Code, 2x Longer Builds
- vLLM vs TGI vs TensorRT-LLM: LLM Serving Latency and Throughput on One H100, Measured at p99
- Go vs Node.js for a Small JSON API: 4-6x Throughput, 6x Less Memory, and What Node Still Wins
- pgvector vs Qdrant: Vector Search Latency on 1M Embeddings, Measured at p99
- pg vs Prisma vs Drizzle: PostgreSQL Driver Latency from Node.js 22, Measured with autocannon
- Swift vs Rust for a Data-Crunching CLI: Where Idiomatic Swift Loses 5x and How Much You Get Back
- gRPC Server-Streaming vs REST Long-Polling Under Load: p50, p99, Connections and CPU on .NET 8
- Python vs Rust in a Hot Loop: What 10 Million Iterations Cost, Measured with hyperfine
- gRPC vs REST JSON: What the Protocol Actually Buys You, Measured on .NET 8 and Go
- Python vs Go for a Batch Log-Processing Job: Wall Time, Memory, Lines of Code and the Day-Two Costs
- Zig vs C for a Systems Tool: Throughput, Binary Size, Cross-Compiling and Where the Bugs Hide
- Node.js 22 vs Deno 2 vs Bun 1.1: HTTP JSON API Throughput, Measured with wrk
- Regex Engine Performance: Rust regex vs Go regexp vs .NET 8 Regex vs Node 22, Measured with hyperfine
- Rust vs Go for a CLI Tool: Startup, Binary Size, Build Time and the Day-Two Costs
- TypeScript vs Kotlin for Backend Services: Type Safety, Tooling, Performance and Team Velocity
- Java 21 Virtual Threads vs .NET 8 async/await: Blocking I/O Throughput, Measured with wrk
- Go Goroutines vs .NET Tasks: HTTP Concurrency Throughput, Measured with wrk
- In-Process Cache vs Redis in .NET 8: Where the Microseconds Go, Measured with BenchmarkDotNet