iluvatar-nlp-operator

Benchmarks GEMM, Conv2d, longtail, and Transformer Block operators on Iluvatar BI-V150 GPUs.

7|1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/DeepLink-org/DeepEval-Skills --skill iluvatar-nlp-operator-deeplink-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iluvatar-nlp-operator
Source: https://github.com/DeepLink-org/DeepEval-Skills/tree/main/skills/Iluvatar/nlp/iluvatar-nlp-operator
Command: npx skills add https://github.com/DeepLink-org/DeepEval-Skills --skill iluvatar-nlp-operator-deeplink-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires torch, pandas, and includes scripts (resource) components.

What problem does it solve? Measuring NLP operator performance on Iluvatar BI-V150 GPUs requires manual container setup, CoreX toolchain compilation, benchmark execution, and result formatting, which is error-prone and hard to reproduce. This Skill automates the full evaluation pipeline and produces standardized Result Contract 2.0 output. ## Core Features & Use Cases - Multi-Operator Benchmarking: Runs GEMM (FP16/FP32 via CoreX CUDA), Conv2d (PyTorch 2.7.1/CoreX backend), LongTail-Bench operators, and Transformer encoder/decoder block inference latency tests. - Deterministic Runners and Collectors: Uses dedicated scripts to compile kernels, execute benchmarks with run-scoped tokens, and convert CSV results into validated result.json with summary metrics (avg, p50, p95, min, max latency). - Containerized Workflow: Guides Docker container creation with the prebuilt CoreX 4.4.0 image, volume mounts for project code, results, and logs, plus environment verification steps. - Use Case: An engineer needs baseline latency numbers for GEMM kernels on a BI-V150 card. The Skill starts the container, compiles the CUDA ops with CoreX, runs the FP16/FP32 case CSVs, and emits a validated result.json with per-case and summary latency metrics. ## Quick Start Ask the agent to run the GEMM operator benchmark on the Iluvatar BI-V150 GPU and generate the baseline result.json.

Frequently Asked Questions about iluvatar-nlp-operator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I benchmark GEMM operators on Iluvatar BI-V150 GPUs?

Start the provided CoreX 4.4.0 Docker container, compile the cuda_ops project with cmake against CoreX headers, then run test_gemm.py with the FP16 and FP32 case CSVs. Finally invoke collect_cases.py with --benchmark gemm to generate result.json.

How to measure Conv2d latency with PyTorch on CoreX backend?

Run test_conv.py with the conv CSV, dtype flag, and the torch argument so it uses the PyTorch 2.7.1/CoreX backend rather than legacy cuDNN 7 interfaces. It measures Forward, Backward Filter, and Backward Data total latency per case.

What Docker image is required for Iluvatar operator benchmarking?

The skill uses swr.cn-north-1.myhuaweicloud.com/deeplink/iluvatar-nlp-operator:latest, which preinstalls CoreX 4.4.0, CUDA-compatible toolchain, cuDNN, PyTorch 2.7.1, CMake, and LongTail-Bench dependencies.

Does the skill support multi-node communication operator tests?

Communication operators via ixCCL/MPI are supported only when the resource project provides communication_bench/readme.md and the user explicitly requests it. Multi-node results are not handled by the GEMM, Conv2d, LongTail, or Transformer Block collectors.

Why does the Transformer Block benchmark fail with a fingerprint error?

The collector rejects results whose aibench_workload_fingerprint does not match the AIBENCH_WORKLOAD_FINGERPRINT environment variable, preventing reuse of stale CSVs. Re-run run_transformer_block.py in the current session so the runner writes the active fingerprint.

Can I reuse old baseline CSVs instead of rerunning benchmarks?

No. The skill explicitly forbids generating results from historical baselines; every run must recompile kernels, execute real measurements, and pass run-token and fingerprint validation before the collector emits result.json.