'performance profiling' 검색 결과

Systematic performance profiling and optimization methodology. Covers CPU profiling, memory profiling, heap analysis, goroutine/thread analysis, FlameGraph generation, latency profiling, database query profiling, network I/O profiling, and continuous performance regression detection. USE WHEN: investigating performance issues, optimizing slow code, reducing memory usage, diagnosing GC/CPU bottlenecks, finding N+1 queries, analyzing pprof/flamegraph output, or establishing a performance baseline. Triggers on "profiling", "performance analysis", "slow code", "flame graph", "pprof", "heap dump", "memory leak", "CPU spike", "bottleneck".

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

Use when you need to set up Java application profiling to detect and measure performance issues — including trusted preinstalled async-profiler v4.x setup, problem-driven profiling (CPU, memory, threading, GC, I/O), interactive profiling scripts, JFR integration with Java 25 (JEP 518, JEP 520), or collecting profiling data with flamegraphs and JFR recordings. This should trigger for requests such as Improve the code with profiling; Apply Profiling; Refactor the code with profiling; Add profiling support; Collect JFR or async-profiler data for Java performance. Part of Plinth Toolkit

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

Use when you need to refactor Java code based on trusted profiling analysis findings — including reviewing repository-owned or maintainer-sanitized docs/profiling-problem-analysis and docs/profiling-solutions files, identifying specific performance bottlenecks, and implementing targeted code changes to address CPU, memory, or threading issues. This should trigger for requests such as Refactor the code with profiling; Apply profiling; Optimize hot path; Reduce allocations found in profiling; Fix CPU bottlenecks from profiling analysis. Part of Plinth Toolkit

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

Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading; Compare before and after profiling results; Check for performance regressions after refactoring. Part of Plinth Toolkit

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

application-performance-performance-optimization workflow skill. Use this skill when the user needs Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

application-performance-performance-optimization workflow skill. Use this skill when the user needs Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Measure code performance and run benchmarks to investigate slow operations, regressions, or memory pressure. Establish a baseline, compare results under matching conditions, report variability, and rerun correctness tests after optimization.

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

• Investigate slow operations
• Compare performance before and after a change
• Measure performance when memory pressure occurs

Coordinate specialist agents to investigate and improve application performance across databases, backend services, frontend code, and delivery infrastructure. Establish baseline measurements, address observed bottlenecks, validate changes with load tests, and set up monitoring to detect future slowdowns.

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

• Finding bottlenecks across an entire application
• Coordinating database, backend, and frontend improvements
• Validating performance changes with load tests

Review game code for likely performance bottlenecks in processing, memory, rendering, and data loading. Compare available estimates with configured limits and produce ranked optimization recommendations, including expected impact, effort, risks, and areas needing runtime measurement.

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

• Finding performance bottleneck candidates in one game system
• Reviewing performance across the whole game
• Comparing available estimates with configured performance limits

Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. This should trigger for requests such as Analyze JFR profile; Analyze the profile; Analyze the performance; Analyze the memory; Analyze the threading; Analyze GC logs from profiling; Prioritize Java profiling bottlenecks by impact. Part of Plinth Toolkit

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

Performance optimization specialist for profiling, caching, and latency optimizationUse when "performance, latency, slow query, profiling, caching, optimization, N+1, connection pool, p99, performance, profiling, caching, latency, optimization, async, database, load-testing, ml-memory" mentioned.

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

Expert at diagnosing and fixing performance bottlenecks across the stack. Covers Core Web Vitals, database optimization, caching strategies, bundle optimization, and performance monitoring. Knows when to measure vs optimize. Use when "slow page load, performance optimization, core web vitals, bundle size, lighthouse score, database slow, memory leak, optimize performance, speed up, reduce load time, performance, optimization, core-web-vitals, caching, profiling, bundle-size, database" mentioned.

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

Find and fix slow page loads, API responses, and database queries using measurements. Compare results before and after each change, discard changes without clear gains, and add checks or monitoring to catch future slowdowns.

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

• Investigating slow page loads and sluggish interactions
• Reducing API delays and repeated database queries
• Checking whether a recent change caused a slowdown

Use TensorBoard to visualize training loss and accuracy, compare experiments, and inspect model structure. Guides logging for PyTorch and TensorFlow, including weight distributions and performance profiling to investigate training problems and processing bottlenecks.

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

• Monitoring training loss and accuracy
• Comparing experiments with different training settings
• Inspecting weight and gradient distributions

Write and refactor C++20/23 applications, addressing memory management, concurrency, and performance bottlenecks. Produce interfaces, implementations, tests, and relevant CMake updates, then check runtime errors and measure performance before applying targeted optimizations.

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

• Refactoring existing code with C++20/23 features
• Investigating memory errors and undefined behavior
• Improving performance through profiling and benchmarks

Diagnose slow loading, high memory use, and low frame rates in USD 3D scenes. Coordinate scene structure checks, validation, optimization, and before-and-after performance comparisons, then produce a report documenting findings and changes.

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

• Investigating slow USD scene loading
• Diagnosing low frame rates in CAD scenes
• Investigating high GPU or system memory use

Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while `samber/cc-skills-golang@golang-performance` provides the optimization patterns.

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

Performance optimization mindset - knowing when to optimize, how to measure, where bottlenecks hide, and when "fast enough" is the right answerUse when "slow, performance, optimize, profiling, benchmark, latency, throughput, cache, n+1, bottleneck, memory leak, too slow, speed up, response time, performance, optimization, profiling, caching, latency, throughput, big-o, benchmarking" mentioned.

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

Performance profiling and optimization for web apps — Core Web Vitals (LCP, INP, CLS), Lighthouse audits, bundle analysis, backend profiling (CPU, memory, DB queries), N+1 detection, caching strategies (Redis, CDN, HTTP), and performance budgets. Use when user asks to improve performance, run Lighthouse audit, profile a Node.js app, optimize Core Web Vitals, reduce bundle size, or investigate slow response times. Do NOT use for database schema optimization (use db-sculptor), Docker image optimization (use docker), or CDN configuration.

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

Performance optimization and measurement for .NET applications. Navigation skill covering Span, ArrayPool, memory management, benchmarking, profiling, Native AOT, and optimization patterns. For building high-performance applications. Keywords: performance, optimization, span, arraypool, benchmarking, profiling, memory, gc, aot, native-aot

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

Use TensorBoard to visualize training loss and accuracy, compare experiments, and inspect model structure. Includes PyTorch and TensorFlow logging examples for examining weight distributions, predictions, and performance bottlenecks during machine learning training.

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

• Comparing loss and accuracy across training runs
• Inspecting weight and gradient distributions
• Exploring embeddings in two or three dimensions

Investigate slow rendering, uneven scrolling, and excessive updates in SwiftUI apps by reviewing code first. When needed, use runtime measurements to assess likely causes, prioritize fixes, and compare performance before and after changes.

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

• Investigate uneven scrolling and dropped frames
• Find causes of excessive view updates
• Review high CPU use or memory growth

Profile app launches and individual user flows in iOS Simulator with ETTrace. Collect traces with readable function names, identify CPU-heavy call stacks, and compare performance changes when recording conditions are consistent.

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

• Investigating slow app launches
• Finding CPU-heavy work during a specific interaction
• Comparing performance before and after a change

Guide performance profiling for Apple platform apps with Instruments, Xcode diagnostics, and MetricKit. Use when investigating app hangs, stutters, high CPU, memory leaks, memory growth, OOM crashes, slow launch, battery drain, thermal issues, App Store performance readiness, or when adding os_signpost and measurement hooks.

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