DeepGEMM vs qmd

DeepGEMM is DeepSeek's open-source library of highly optimized FP8 General Matrix Multiplication (GEMM) kernels targeting NVIDIA SM90/SM100 GPUs — the H100, H800, and Blackwell class. The headline feature is a lightweight just-in-time (JIT) compiler that eliminates the need for offline CUDA compilation at install time, dramatically lowering the barrier for teams who want raw GPU throughput without complex build pipelines. The library covers FP8 and FP4 dense GEMMs, BF16 accumulation, grouped GEMMs for Mixture-of-Experts architectures with overlapped NVLink communication, and multi-query attention scoring kernels. On H800 hardware DeepGEMM posts up to 1,550 TFLOPS — competitive with hand-tuned vendor libraries — while remaining fully open source under the MIT license. For LLM inference teams running on H100/H800 clusters, DeepGEMM slots directly into inference stacks like vLLM and SGLang. It's especially notable because it came from DeepSeek's internal training infrastructure, meaning it's been battle-tested at the scale that produced some of 2026's most cost-efficient models. This isn't research code — it's production tooling going public.

qmd is a lightweight local search engine built by Tobi Luetke, CEO of Shopify, for indexing and querying personal knowledge bases, documentation, and meeting notes — entirely offline. It combines three retrieval approaches in a single pipeline: BM25 full-text search for exact keyword matches, vector semantic search via ONNX-based embeddings, and LLM re-ranking using GGUF models through node-llama-cpp. All three stages run locally with no cloud dependency. The tool ships in multiple deployment modes: a CLI for ad-hoc queries, a Node.js library for programmatic use, an HTTP service for local API access, and — most useful for AI workflows — a native MCP server that lets Claude Code, Cursor, and similar editors query your local knowledge base directly during coding sessions. The hybrid retrieval approach means it handles both "find the exact error message from last week's standup notes" and "what was our decision about the auth architecture" equally well. What makes this notable beyond its technical approach is provenance: Luetke shipped it as a personal tool he actually uses, not a startup product. The GitHub history shows active iteration and he's been talking about it on X. It's a credible signal of where pragmatic AI-augmented knowledge management is heading for technical users who prefer local-first tools.