SShortSingh.
Back to feed

nano-vLLM Benchmarked on RTX 3090: Key Insights Into LLM Serving Performance

0
·1 views

A developer analyzed nano-vLLM, a compact ~1,200-line Python LLM serving engine, by modeling its prefill and decode costs using Qwen3-0.6B BF16 on a single RTX 3090 GPU. During cold prefill, the engine utilized roughly 76–84% of the GPU's measured BF16 compute capacity, while single-request decode aligned closely with a memory-traffic model estimating 531–562 GB/s of weight and KV data movement. Batching proved highly effective, scaling total decode throughput from 334 tokens per second at batch size 1 to 4,794 tokens per second at batch size 128. Longer prompt histories were found to reduce decode speed, as growing key-value cache reads add memory overhead per token. The study highlights that prefill and decode stress fundamentally different hardware resources, with batching amortizing weight costs and longer contexts increasing KV cache traffic.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Publishing a Browser Extension in 2026 Is Far Harder Than Tutorials Suggest

Developers hoping to publish a browser extension face a lengthy, multi-stage review process that goes well beyond writing code and hitting upload. The Chrome Web Store alone hosts roughly 303,800 extensions as of mid-2026, with nearly 50,000 new ones added in a single quarter, meaning every submission enters an increasingly crowded queue. Before even reaching the dashboard, developers must prepare multiple icon sizes, high-resolution screenshots, promotional tiles, detailed store copy, a valid privacy policy, and ideally translations across 40-plus locales. While AI agents can now accelerate asset creation and copywriting, they cannot navigate review queues or respond to store reviewers on a developer's behalf. Every error during review resets the clock, making the post-coding publication phase a slow, high-stakes gauntlet rather than a simple final step.

0
ProgrammingDEV Community ·

WPS Embraces MCP Protocol, Letting AI Agents Directly Edit Office Documents

Kingsoft Office (WPS) has adopted the Model Context Protocol (MCP), enabling AI tools like Claude and Cursor to directly create and edit Word, Excel, and PowerPoint files without manual copy-pasting. MCP, developed by Anthropic and described as a universal 'USB-C standard' for AI integrations, allows any compatible AI client to interface with supported services through a unified protocol. Three open-source projects on GitHub — most notably wps-skills, with 243 available tools — give individual developers a ready-made MCP server to connect their AI agents to WPS. Setup requires Node.js, a local WPS installation, and a configuration file pointing AI clients to the server via an absolute file path. Once configured, developers can issue natural-language commands to automate document creation, spreadsheet edits, and even multi-page presentation generation entirely within WPS.

0
ProgrammingDEV Community ·

Developer open-sources bilingual Bazi terminology database and React chart component

A developer has released bazi-kit, an MIT-licensed open-source monorepo designed to simplify building software around Bazi, the Chinese Four Pillars of Destiny system. The toolkit includes two packages: bazi-terms, a zero-dependency bilingual (Chinese/English) terminology database, and bazi-chart, a React component for rendering Bazi charts from any data source. A core design principle is that bazi-kit performs no calculations itself, instead acting purely as a presentation and vocabulary layer that works with any existing calculation engine. The project addresses a longstanding problem in the Bazi software ecosystem where terminology, math, and rendering are typically bundled together, making it difficult to swap engines or reuse components. By open-sourcing only the vocabulary and UI layers, the library aims to serve as generic infrastructure that any Bazi application can adopt without exposing proprietary interpretation logic.

0
ProgrammingDEV Community ·

Message Queues Explained: When and Why to Use Them in Backend Systems

Message queues allow backend applications to offload slow or non-critical tasks — such as video processing or sending notifications — from the main API request, so users receive faster responses. Instead of waiting for every operation to complete, the API saves the request, places a message in a queue, and lets background workers handle the rest. This approach improves scalability, reliability, and service decoupling, with popular tools including Kafka, RabbitMQ, and Amazon SQS. However, message queues introduce added complexity, requiring developers to manage concerns like duplicate messages, retries, ordering, and monitoring. Experts advise using them only when genuinely needed — such as for high-traffic systems or background processing — rather than as a default architectural choice.

nano-vLLM Benchmarked on RTX 3090: Key Insights Into LLM Serving Performance · ShortSingh