exec-slurm-compile

Compile TensorRT-LLM on a SLURM cluster via enroot container batch jobs.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill exec-slurm-compile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exec-slurm-compile
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/TensorRT-LLM/exec-slurm-compile
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill exec-slurm-compile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines compiling TensorRT-LLM on a remote SLURM cluster by coordinating container preparation, job submission, live monitoring, and build verification so you don’t need to compile directly on your local machine.

Core Features & Use Cases

  • SLURM batch compilation workflow: Submits a containerized compilation job using sbatch and runs the build inside an enroot container.
  • enroot container pre-dumping: Optionally pre-imports the Docker image into a .sqsh image via a dedicated SLURM job to reduce compile-time download overhead.
  • Live monitoring and log-based verification: Actively polls SLURM status, tails the srun log, and validates success via SLURM exit code and build log messages.
  • Use Case: You need to build TensorRT-LLM for a specific GPU architecture on a cluster partition with the right TensorRT environment packaged in an NVIDIA container.

Quick Start

Use the enroot-import step to generate a .sqsh from the TensorRT-LLM Docker image, then submit the compilation with sbatch using that .sqsh, your TensorRT-LLM repo path, and your SLURM partition and account.

Frequently Asked Questions about exec-slurm-compile

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

FAQPage Schema
How do I compile TensorRT-LLM on a SLURM cluster?

To compile TensorRT-LLM on a SLURM cluster, you can submit a containerized batch job using sbatch that runs the build inside an enroot container, allowing remote and repeatable compilation.

What is the best way to reduce download overhead when building TensorRT-LLM remotely?

Pre-importing your Docker image into a .sqsh file using enroot pre-dumping reduces download overhead during the TensorRT-LLM build by preparing the container image via a dedicated SLURM job beforehand.

Do I need a pre-built .sqsh container image to run a TensorRT-LLM SLURM compilation job?

You need either a pre-built .sqsh container image or a Docker image URL to import, along with access to your TensorRT-LLM repository directory and correct SLURM partition and account parameters.

How does SLURM job monitoring work for remote containerized builds?

SLURM job monitoring actively polls job status, tails the srun log, and validates build success by checking the SLURM exit code alongside specific build log messages for verification.

Can I target a specific GPU architecture when compiling TensorRT-LLM via SLURM?

Yes, you can target a specific GPU architecture by submitting the compilation job to a SLURM cluster partition that has the correct TensorRT environment packaged in an NVIDIA container.