AINewsnow

We built an open-source GPU profiler you point an AI agent at, instead of reading traces yourself

This story is from 2026-09-17. It is preserved in the archive; the latest stories are on the live feed.

We've been tuning vLLM/SGLang/llama.cpp setups for a long time and got tired of the profiling part: nsys trace, open the GUI, squint, change a flag, repeat. The profilers assume a human is looking at the timeline. These days the thing doing our tuning is usually an agent, and it can't look at a tim…

Read the full story at r/LocalLLaMA ↗

Timeline · 1 report

  1. 2026-09-17 12:27 · r/LocalLLaMA
    We built an open-source GPU profiler you point an AI agent at, instead of reading traces yourself

More stories

  1. Qwen3.8-Flash-Next-Heretic2-IQ4XS on Halogen Flash Server vs llama-server on Strix Halo: 2.3-7.7x prefill speedup with half the VRAM (+ vision works on BYO GGUF) — r/LocalLLM
  2. M2 Mac ultra128gb Qwen flash next — r/LocalLLM
  3. Multi-hour llama.cpp optimization experiments on Qwen MoE models, patches, benchmarks, and reproduction guides — r/LocalLLM
  4. CUDA: enable sparse fa for qwen4 by am17an · Pull Request #28770 · ggml-org/llama.cpp — r/LocalLLaMA
  5. focus-llama: a llama.cpp fork implementing Declarative Attention (arXiv:2609.02737) — r/LocalLLaMA
  6. I ran Opencode and PI against the same local model on 3 identical projects, same prompts, same hardware... — r/LocalLLM
  7. I benchmarked 13 model/quant configs on a GPU with no tensor cores (Vega iGPU + Vulkan) and wrote it up as a measurement study — the quant encoding suffix matters more than you'd think — r/LocalLLM
  8. M1 Max 32GB, trying to run Qwen 3.8 27B at decent speeds and context — r/LocalLLaMA

Get the daily brief of stories like this at 6:30 every morning →