'performance profiling' 검색 결과

Performance profiling principles. Measurement, analysis, and optimization techniques.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Learns from DAG execution history to improve future performance. Identifies successful patterns, detects anti-patterns, and provides recommendations. Activate on 'learn patterns', 'execution patterns', 'what worked', 'optimize based on history', 'pattern analysis'. NOT for failure analysis (use dag-failure-analyzer) or performance profiling (use dag-performance-profiler).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

NVIDIA RAG Blueprint performance-tuning guidance for profiling retrieval stacks, comparing bottlenecks, and validating latency or throughput improvements.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and improve SwiftUI runtime performance. Use when diagnosing slow rendering, janky scrolling, high CPU, memory usage, excessive view updates, layout thrash, body evaluation cost, identity churn, view lifetime issues, lazy loading, Instruments profiling guidance, and performance audit requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React performance: production-level waterfalls, dynamic import, render profiling. Use when implementing, reviewing or testing react performance for React, Vite, Next.js or Perfect_AI projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performance profiling principles. Measurement, analysis, and optimization techniques.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performance optimization, profiling, caching strategies, lazy loading, bundle optimization, and monitoring. Use when optimizing application performance, reducing bundle size, implementing caching, or analyzing bottlenecks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Measure, profile, and fix performance bottlenecks — Core Web Vitals, backend latency, bundle size, and database queries. Load when performance requirements exist, users report slowness, profiling reveals bottlenecks, or the user asks to optimize load time, LCP, INP, CLS, or response time. Not for premature optimization without evidence. Pairs with browser-testing-with-devtools and ci-cd-and-automation for regression guards.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Learns from DAG execution history to improve future performance. Identifies successful patterns, detects anti-patterns, and provides recommendations. Activate on 'learn patterns', 'execution patterns', 'what worked', 'optimize based on history', 'pattern analysis'. NOT for failure analysis (use dag-failure-analyzer) or performance profiling (use dag-performance-profiler).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identifies API latency hotspots and bottlenecks with profiling tools, slow endpoint detection, suspected causes, and fix roadmap. Use for "latency profiling", "performance bottlenecks", "slow APIs", or "backend performance".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Launch an SGLang server, run a quick accuracy check, and capture an execution trace for performance inspection. Return the trace location and generated files, ready to open in Perfetto or Chrome tracing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Capture an execution trace of SGLang inference
• Check basic accuracy before profiling
• Record input processing and token generation separately

Helps write and improve Python code with type hints, tests, and organized package settings. Covers dependency management, asynchronous tasks that wait on external operations, and profiling to identify performance bottlenecks before making changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refactoring Python code with type hints and tests
• Organizing package settings and dependencies
• Implementing concurrent input and output tasks

Set up application monitoring with structured logs, performance metrics, and traces that follow requests across services. Build dashboards and alerts, run load tests, investigate CPU and memory bottlenecks, and estimate future infrastructure capacity.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set up application dashboards and alerts
• Investigate production issues using logs, metrics, and traces
• Run load tests before traffic increases

Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling/tracing .NET code (dotnet-trace, PerfView), production telemetry, or load/stress testing (Crank, k6).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides React Native performance optimization guidelines for FPS, TTI, bundle size, memory leaks, re-renders, and animations. Applies to tasks involving Hermes optimization, JS thread blocking, bridge overhead, FlashList, native modules, or debugging jank and frame drops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and render fanout, implement semantically safe fixes, and verify behavior plus repository budgets. Use for trace files, reported profiling durations or call chains, dropped frames, long tasks, resize or scroll jank, render storms, layout thrashing, selector hot paths, interaction latency, or requests to locate exact source-level bottlenecks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Visualize training metrics, debug models with histograms, compare experiments, visualize model graphs, and profile performance with TensorBoard - Google's ML visualization toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Produce a prioritized performance-optimization roadmap across frontend, backend, and infrastructure. Use as an explicit/manual helper after bottlenecks are known or suspected, not as the owner of regression detection, profiling capture, or test execution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compare current benchmark results against historical baselines to spot performance regressions. Use as an explicit/manual helper for build-to-build degradation review, not for broad optimization strategy or low-level profiling ownership.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Performance benchmarking for a deployed NVIDIA RAG Blueprint server: profiling pass + aiperf load test driven by a single YAML config. Not for accuracy / RAGAS scoring (use rag-eval) or for deploying / repairing services (use rag-blueprint).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See `samber/cc-skills-golang@golang-benchmark` and `samber/cc-skills-golang@golang-performance` skills).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers), database/query optimization, autoloaded options, object caching, cron, HTTP API calls, and safe verification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when an Apple-platform app feels slow, memory grows, battery drains, or ANY performance issue needs diagnosing. Covers memory leaks, profiling, Instruments workflows, retain cycles, optimization.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.