distributed-blocks
Operate Petals RemoteSequential block sequences, local block loading, quantization, tensor-parallel conversion, dtype constraints, and speculative Llama block internals.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- distributed-blocks
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Operate Petals RemoteSequential block sequences, local block loading, quantization, tensor-parallel conversion, dtype constraints, and speculative Llama block internals.
- disable-model-invocation
- true
02 资源文件 4
- 参考文档references/api-reference.md1.3 KB
- 参考文档references/troubleshooting.md1012 B
- 参考文档references/workflows.md1.3 KB
- 脚本scripts/inspect_block_api.py2.7 KB
03 SKILL.md 正文
Petals Distributed Blocks
Use this sub-skill for block-level Petals tasks involving RemoteSequential, remote transformer block chains, hidden-state tensors, load_pretrained_block, QuantType, convert_block, tensor-parallel devices, DHT prefix alignment, or speculative Llama internals.
Read references/api-reference.md, references/workflows.md, and references/troubleshooting.md. Use python scripts/inspect_block_api.py --help for a no-network API inspection.
Route ordinary .generate() usage to client-inference, server launch flags to server-swarms, prompt training to prompt-tuning, and benchmarks to benchmarks-maintenance.
Checklist: RemoteSequential.forward() takes hidden states shaped [batch, seq, hidden]; block slices must be inside model layer bounds; clients and servers must agree on DHT prefix and block indices; deep prompts must match sliced block count; quantization requires a compatible optional backend.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).