Agent skill

langfuse-performance-tuning

Optimize Langfuse tracing performance for high-throughput applications. Use when experiencing latency issues, optimizing trace overhead, or scaling Langfuse for production workloads. Trigger with phrases like "langfuse performance", "optimize langfuse", "langfuse latency", "langfuse overhead", "langfuse slow". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-performance-tuning --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Version: 1.12.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEdit
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-performance-tuning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Langfuse Performance Tuning ## Overview Optimize Langfuse tracing for minimal overhead and maximum throughput: benchmark measurement, batch tuning, non-blocking patterns, payload optimization, sampling, and memory management. ## Prerequisites - Existing Langfuse integration - Performance baseline to compare against - Understanding of async patterns ## Performance Targets | Metric | Target | Critical | |--------|--------|----------| | Trace creation overhead | < 1ms | < 5ms | | Flush latency (batch) | < 100ms | < 500ms | | Memory per active trace | < 1KB | < 5KB | | CPU overhead | < 1% | < 5% | ## Instructions ### Step 1: Benchmark Current Performance ```typescript // scripts/benchmark-langfuse.ts import { performance } from "perf_hooks"; import { startActiveObservation, updateActiveObservation } from "@langfuse/tracing"; import { LangfuseSpanProcessor } from "@langfuse/otel"; import { NodeSDK } from "@opentelemetry/sdk-node"; async function benchmark() { const sdk = new NodeSDK({ spanProcessors: [new LangfuseSpanProcessor()], }); sdk.start(); const iterations = 1000; // Measure trace creation const timings: number[] = []; for (let i = 0; i < iterations; i++) { const start = perfo

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Performance Targets
  4. Instructions
  5. Step 1: Benchmark Current Performance
  6. Step 2: Optimize Batch Configuration
  7. Step 3: Non-Blocking Trace Wrapper
  8. Step 4: Payload Size Optimization
  9. Step 5: Sampling for Ultra-High Volume
  10. Step 6: Memory Management
  11. Optimization Impact Matrix
  12. Error Handling
  13. Resources
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the langfuse-performance-tuning skill do?

Optimize Langfuse tracing performance for high-throughput applications. Use when experiencing latency issues, optimizing trace overhead, or scaling Langfuse for production workloads. Trigger with phrases like "langfuse performance", "optimize langfuse", "langfuse latency", "langfuse overhead", "langfuse slow". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-performance-tuning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going