Skip to content
View holtwood's full-sized avatar

Organizations

@holtwood-systems

Block or report holtwood

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
holtwood/README.md

Shane / holtwood

Systems engineer working on AI infrastructure, GPU kernels, and performance-critical software.

C++ · CUDA · Triton · Rust · HPC

I care about the part after the benchmark: whether a performance claim survives a different shape, a different machine, and a clean rebuild.

做 AI Infra / HPC 系统,关心性能结论能否被复现。

Open to: AI Infra / HPC / performance engineering roles and technical collaboration.

Website · Systems · Arena · Forks · Email


Start here

Three public organizations, each with a different job:

Organization What it is
Systems holtwood-systems Original AI Infra / HPC work: kernels, inference runtime, serving control plane, reproducible evidence
Arena holtwood-arena Competition and benchmark record: CANN / FlagOS / Kunpeng / Muse, plus the public race lab
Forks holtwood-forks Upstream reading copies. No original work claimed; useful for source study and minimal repros

The curated entry point is imshane.site/projects. GitHub is the implementation layer, not the only map.

Selected work

Project What it is Signal
paged-serving Rust LLM serving control plane: paged KV, continuous batching, OpenAI-compatible SSE, C ABI to a real CUDA backend control/data plane boundary
tiny-llm CUDA/C++ inference runtime: GGUF, W8A16, tokenizer, paged KV, CUDA Graphs end-to-end runtime
cuflash FlashAttention from scratch in CUDA C++: scalar → WMMA tensor cores, FlashDecoding / Split-KV kernel depth
trifuse Fused Triton kernels (RMSNorm+RoPE, gated MLP, FlashAttention) registered through torch.library kernel breadth + integration
cuda-foundations A reproducible CUDA operator path: SGEMM ladder → reusable kernels → inference components teaching by construction
race Performance engineering lab: Speed Demon, 1BRC, PPC, DIMACS, AHC; every number bound to hardware and commit competition discipline

Full map: holtwood-systems/portfolio.

Also: kvtier (KV cache tiering experiments) · ai-infra-radar (upstream contribution radar, personal).

Competition work

I use competitions as a forcing function for measurement discipline.

  • CANNJudge / Ascend 910B2 — CANN 2026 electricity-industry operator special (10 problems) and October ladder (4 problems), plus the earlier CANN challenge. Private workspaces are retained as archives; public methodology is in holtwood-arena.
  • Kunpeng HPC — S2 convolution optimization (public, x86-verified; Kunpeng platform not re-measured) and S3 OpenFOAM static study (public, archived; not entered).
  • FlagOS S2 — SGLang kernel optimization and MiniCPM5-2B inference throughput workspaces.
  • Muse Spark Open Kernel Challenge — kernel and serving tracks.

Public workspaces: kunpeng-s2-conv · kunpeng-s3-openfoam · race.

Competition rules and other teams' work are respected: private workspaces stay private while the rules require it; public pages carry only sanitized, reproducible material.

Before systems

I came to AI infrastructure through genomics and real-time systems: BGI (genomic-scale data workflows), Mindray (medical imaging), ZEGO (RTC). That background is why I care about memory bounds, I/O behavior, and end-to-end latency — not just kernel microbenchmarks.

The genomics work is archived under open-genomics in maintenance mode. The earlier application/tooling projects remain at holtwood-projects.

How I scope claims

  • Local / CPU correctness is not device correctness.
  • Device correctness is not platform acceptance.
  • A benchmark is only as useful as its hardware, shape, build, command, and variance record.
  • If a claim does not survive a clean rebuild, it is not a result yet.

Elsewhere

Pinned Loading

  1. holtwood-systems/paged-serving holtwood-systems/paged-serving Public

    Rust LLM Serving 控制面:Paged KV、continuous batching、OpenAI SSE、C ABI 后端与可信压测

    Rust 1

  2. holtwood-systems/cuflash holtwood-systems/cuflash Public

    cuflash — FlashAttention from scratch in CUDA C++: scalar → WMMA tensor-core forward, FlashDecoding/Split-KV, Roofline analysis. FP16/BF16/FP32 fwd/bwd, sm_70–sm_90.

    Cuda 1

  3. holtwood-systems/tiny-llm holtwood-systems/tiny-llm Public

    CUDA/C++ LLM 推理运行时:GGUF、W8A16、tokenizer、Paged KV、CUDA Graph 与可复现基准

    C++

  4. holtwood-systems/cuda-foundations holtwood-systems/cuda-foundations Public

    可验证的 CUDA 学习主线:SGEMM、通用 GPU 算子、性能优化与轻量推理组件

    C++ 11

  5. holtwood-systems/trifuse holtwood-systems/trifuse Public

    面向 Transformer 推理的可验证 Triton 融合算子与 torch.library 集成

    Python 4

  6. holtwood-arena/race holtwood-arena/race Public

    性能工程竞赛实验室:Speed Demon / 1BRC / PPC / DIMACS / AHC 的练习与研究,数字绑定硬件与证据

    Python