ZMC2019's picture
400 tasks: kernel-optimization agent, profiler permissions, relaxed exact gates (part 9)
74edf23 verified
Raw History Blame Contribute Delete
1.61 kB
schema_version = "1.1"
[task]
name = "mle-bench/persistent-kv-append-inline"
description = "Every serving stack does append-then-attend as two kernels, because a kernel boundary is a free device-wide fence. Fuse them and you have to rebuild that guarantee yourself: a release fence after a scattered page write, a grid-wide barrier, an acquire on the other side -- for a store whose address came out of a shuffled page table and whose reader is a different block. This task allows ONE launch, so the boundary genuinely has to go."
authors = []
keywords = ["mle", "kernel-generation", "megakernel", "persistent-kernel", "paged-attention", "kv-cache", "grid-sync", "memory-model", "gqa", "decode"]
[metadata]
suite = "mle-bench"
group = "kernel-generation"
level = "1.0"
difficulty = "hard"
category = "mle"
tags = [ "mle", "kernel-generation", "kernels", "gpu", "real-world",]
[verifier]
timeout_sec = 2700.0
[agent]
timeout_sec = 14400.0
# GPU request: honored by Modal/GKE/Daytona. On the local docker backend set environment.override_gpus: 0
# in the job config and attach a GPU via configs/gpu_overlay_nvidia.yaml (see RUNNING.md §5).
# Profiling: `ncu` needs GPU performance counters — the runner must add the SYS_ADMIN capability
# (docker `--cap-add SYS_ADMIN`) or the host must set NVreg_RestrictProfilingToAdminUsers=0.
# Without it ncu exits with ERR_NVGPUCTRPERM. `nsys` works without any extra capability.
[environment]
build_timeout_sec = 3600.0
cpus = 8
memory_mb = 65536
storage_mb = 40960
gpus = 1
network_mode = "public"
mcp_servers = []
[verifier.env]
[environment.env]
[solution.env]