'benchmark' 검색 결과

Explain portfolio performance by separating the effects of sector allocation, stock selection, market factors, and timing. Compare results with a benchmark, assess risk-adjusted returns, and prepare a report showing where excess returns came from.

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

• Explaining returns above or below a benchmark
• Separating sector allocation and stock-selection effects
• Assessing market exposure and trading timing

Analyze social media post data to calculate engagement, click rates, and estimated returns on advertising spend. Compare results with supplied platform benchmarks, identify strong and weak posts, and generate recommendations for improving campaign performance.

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

• Review social campaign performance
• Identify posts with strong or weak engagement
• Estimate advertising returns and interaction costs

Create, update, run, and debug shell-based performance scenarios for the but CLI. It separates repository setup from the operation being measured, uses Hyperfine for timing, and guides focused validation and inspection of test output.

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

• Add a performance scenario for a but CLI operation
• Update repository fixtures for an existing benchmark
• Run a short benchmark for one scenario

Turn a broad robotics research direction into ranked ideas with concrete benchmarks and simulation plans. The workflow combines literature review, novelty checks, and external critique while accounting for hardware access, safety, evaluation metrics, and failure cases.

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

• Explore research topics in manipulation or navigation
• Plan simulation studies before using physical robots
• Check novelty and feasibility of robotics ideas

Build Go services and command-line tools with clear interfaces, explicit error handling, and concurrent tasks using goroutines and channels. Use pprof to investigate performance, then check behavior with benchmarks, structured test cases, fuzzing, and race detection.

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

• Implementing concurrent tasks with cancellation and error handling
• Building gRPC or REST services and command-line tools
• Investigating Go performance with pprof and benchmarks

Run concurrent Omnigent conversations with real hosts and runners while replacing the LLM with a zero-latency mock. Read the generated report to explain response-time distributions, throughput, and failures, helping assess Omnigent's own processing overhead.

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

• Measuring performance with concurrent hosts
• Studying latency as conversation history grows
• Comparing throughput and failures under load

Refresh evidence behind paid advertising guidance by checking platform changes, APIs, policies, regulations, and benchmarks. Record sources and contradictions, flag outdated or unsupported claims, and propose updates grounded in current primary sources.

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

• Refreshing overdue advertising research
• Rechecking platform and API claims
• Reviewing evidence behind advertising benchmarks

Evaluate a local Codex plugin to understand its scores and identify what to fix first. Review stronger and weaker skills, prepare benchmark runs, compare saved results across versions, and produce a readable report.

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

• Review an entire plugin before comparing versions
• Understand scores and prioritize fixes
• Compare strengths and weaknesses across included skills

Evaluate a local Codex skill for metadata, structure, reference links, size, and helper code quality. Get prioritized fixes and explanations, with benchmark setup for deeper analysis and measurement recommendations when observed usage is available.

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

• Audit a local Codex skill
• Understand evaluation scores and findings
• Prioritize skill improvements

Investigate observed slowdowns or increased CPU, memory allocation, and IO costs in a process you control. Use controlled timing and runtime-specific profiling tools to test a cause, then check performance and behavior after a fix.

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

• Investigate a command that has become slower
• Locate CPU or memory allocation hotspots
• Separate transport waits from backend processing costs

Compare baseline and current Pinot benchmark results from JMH, a tool for measuring code performance. The skill uses a separate baseline worktree, a working directory kept apart from the current code.

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

• Compare Pinot benchmarks before and after a code change
• Check performance differences against a baseline
• Keep baseline code in a separate working directory

Optimize .NET loops with SIMD, which processes multiple values in one operation, or review existing SIMD code. Check behavioral equivalence, memory safety, platform fallbacks, and benchmarks to establish whether the optimization is correct and worthwhile.

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

• Optimize numeric loops with SIMD
• Review existing vectorized code for correctness
• Test boundary lengths and overlapping buffers

Runs HTTP load tests with gradually increasing concurrent connections. It measures response-time percentiles, throughput, and errors, identifies where performance starts to deteriorate, and recommends a concurrency level based on the results.

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

• Benchmarking an API under increasing load
• Finding concurrency levels where p99 latency rises
• Checking throughput saturation and error growth

Benchmark indicator performance with BenchmarkDotNet. Use for Series/Buffer/Stream benchmarks, regression detection, and optimization patterns. Target 1.5x Series for StreamHub, 1.2x for BufferList.

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

Evaluates code generation models across HumanEval, MBPP, MultiPL-E, and 15+ benchmarks with pass@k metrics. Use when benchmarking code models, comparing coding abilities, testing multi-language support, or measuring code generation quality. Industry standard from BigCode Project used by HuggingFace leaderboards.

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

Filesystem RAG benchmarks: corpus/, train.json, evaluate_rag.py (RAGAS quality). Not for prod monitoring, latency/throughput benchmarking (use rag-perf), or evals outside this repo layout.

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

Recommend and customize Megatron Bridge library and benchmark recipes for a user's model, GPU count, hardware, sequence length, and pretrain/SFT/PEFT goal. Use when selecting a starting recipe, comparing library and benchmark configs, resizing parallelism for a GPU allocation, or distinguishing convergence changes, semantics-preserving execution tuning, and benchmark-only shortcuts.

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

Benchmark Jetson LLM/VLM serving performance across vLLM, llama.cpp, and Ollama with structured JSON output.

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

Golang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (→ See `samber/cc-skills-golang@golang-benchmark` skill) or debugging workflow (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).

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

Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.

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

Run all reference benchmarks under benchmarks/eval/ and refresh the reference-table cells in benchmark_*.py. Auto-detects host hardware (H200/H100/H800/...). For each row's matching hw entry: replace cells in place. For new hardware or a new workload tag: append a new row to the section's table. Local-Pipeline-Result tables are skipped. One slash command runs everything end-to-end and auto-commits.

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

**WORKFLOW SKILL** - Evaluate AI agent skills using structured benchmarks with YAML specs, fixture isolation, and pluggable validators. USE FOR: run waza, waza help, run eval, run benchmark, evaluate skill, test agent, generate eval suite, init eval, compare results, score agent, agent evaluation, skill testing, cross-model comparison. DO NOT USE FOR: improving skill frontmatter (use waza dev), creating new skills from scratch (use skill-creator), token counting or budget checks (use waza tokens). INVOKES: Copilot SDK executor, mock engine, code/regex validators. FOR SINGLE OPERATIONS: use waza run directly for a single benchmark.

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

Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped `.build-benchmark/` artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.

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

Routes any legal task to the right LLM, like OpenRouter but for legal work and grounded in benchmarks instead of brand loyalty. Built from mid-2026 legal evals (legalbenchmarks.ai, Vals AI × Stanford LegalBench across 124 models, Harvey's Legal Agent Benchmark, the Atticus Project's CUAD/MAUD/ACORD) plus translation evidence (WMT25, SwiLTra-Bench, ArabLegalEval). Covers five verticals: contract drafting, info extraction, legal research, contract review, and legal translation (including Arabic/MENA). Each asks up to four questions (cost, speed, accuracy/stakes, privacy/jurisdiction/language), then returns a primary model, a fallback, what to avoid, and what a human must verify. Core principle: capability is not controllability, so every route ends with a verification step. Not legal advice; a lawyer owns the output.

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