vccs
Vue 3용 차트 컴포넌트 모음, Recharts에서 포팅
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기kernelbench.com — GPU kernel engineering benchmarks for autonomous LLM coding agents. v3 archive + v-hard latest.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Frontier coding agents write GPU kernels. Each session is one autonomous
agent, graded against a roofline (or ms/speedup) ceiling, then reward-hack
audited before anything is published. Live: kernelbench.com.
This monorepo is the website and the evals. GPU sessions launch to
Lambda / Brev (or another remote worker). Operator rules: AGENTS.md, which
points at a specialized AGENTS.md in each directory. Methodology and
history: each bench's SPEC.md and DEVLOG.md.README 전문 보기 ↗Frontier coding agents write GPU kernels. Each session is one autonomous agent, graded against a roofline (or ms/speedup) ceiling, then reward-hack audited before anything is published. Live: kernelbench.com.
This monorepo is the website and the evals. GPU sessions launch to
Lambda / Brev (or another remote worker). Operator rules: AGENTS.md, which
points at a specialized AGENTS.md in each directory. Methodology and
history: each bench's SPEC.md and DEVLOG.md.
| bench | path | what | site |
|---|---|---|---|
| hard | benchmarks/hard/ | per-op kernels (CUDA or Triton), roofline-graded | /hard |
| mega | benchmarks/mega/ | full fused megakernels | /mega |
| cuda | benchmarks/cuda/ | CUDA-only writing deck (Triton/DSL fail) | /cuda |
| mini | benchmarks/mini/ | small-model (<200B) deck, capped + 5-repeat (WIP) | homepage scroll category on / when debuted (not /mini) |
| multi | benchmarks/multi/ | 4×H100 NVLink multi-GPU (WIP, frontier roster) | unpublished |
Hard / mega / cuda share harness machinery and run unlimited wall-clock
(BUDGET_SECONDS=0). Mini is capped; multi is sequential on a 4-GPU node.
Next.js 16 + Tailwind. Package manager is bun (bun.lock):
bun install
bun dev # http://localhost:3000
bun run build
Site data is baked at build time from benchmarks/*/results/
(app/_lib/data.ts). Publish/deploy: kb publish then kb deploy — see
app/AGENTS.md.
app/ public/ the website (app/AGENTS.md); app/_lib/data.ts bakes benchmark data at build time
benchmarks/<bench>/ AGENTS.md, SPEC.md, DEVLOG.md, problems, src, scripts, results/, outputs/runs/ (gitignored archives)
scripts/ shared runner (lib/run_harness.sh), workers, publish helpers
kbtool/ the `kb` CLI (uv package); `uv tool install -e ./kbtool` puts `kb` on PATH
media/ tracked chart generators (media/AGENTS.md); PNGs gitignored
runs/ gitignored HF staging from `kb push-runs` (not a third archive)
This list is closed. A new thing goes in the directory that owns it. kbtool/tests fails on a new top-level dir.
Bench virtualenvs exist only on the GPU boxes that run the benchmark; the
Mac checkout carries kbtool/.venv alone.