frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Carnegie Mellon is putting computer science courses on YouTube for free

https://www.cs.cmu.edu/learn/
539•pcompeau•3h ago•89 comments

Windows 11 Is Collecting Data on Which Coding Agents and Developer Tools You Use

https://xusheng.dev/posts/windows-coding-agent-telemetry/
105•cwaffles•1h ago•48 comments

BugMeNot has closed

https://www.bugmenot.com/
255•lode•3h ago•137 comments

World's Largest Brands Infected With Malware Via Optimizely

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
136•martinald•3h ago•26 comments

How to Break into Security, Ptacek Edition (2012)

https://krebsonsecurity.com/2012/06/how-to-break-into-security-ptacek-edition/
60•ronfriedhaber•2h ago•16 comments

OpenCode Browse

https://opencode.ai/product/browse
84•mfiguiere•3h ago•41 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
293•burntsushi•7h ago•70 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
201•PaulHoule•7h ago•198 comments

Chemistry is Actually Geometry

https://chillphysicsenjoyer.substack.com/p/chemistry-is-actually-geometry
77•sebg•4h ago•21 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
279•geerlingguy•8h ago•197 comments

Optimizely Compromised, Served Malware on Zoom, GitLab

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
39•kristjansson•1h ago•14 comments

Technical issue at JPMorgan Chase triggers online banking delays for US banks

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
696•samk3nny•6h ago•569 comments

Formal Verification Is Not Verifiable

https://alperenkeles.com/posts/formal-verification-is-not-verifiable/
36•zdw•2d ago•5 comments

Rust changed me as a developer

https://blog.startifact.com/posts/how-rust-changed-me/
165•speckx•4h ago•105 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

25•arshpatankar•4h ago•10 comments

Squircles

https://linebender.org/wiki/curves/squircle/
115•raphlinus•16h ago•35 comments

United Airlines experiencing a widespread system outage, airline says

https://www.cnn.com/2026/11/16/us/united-airlines-outage
142•bearsyankees•2h ago•69 comments

Spamhaus new email sender requirements in November

https://www.spamhaus.org/sender-guidelines/
64•computer23•2h ago•49 comments

Do Repeat Yourself

https://arcentry.com/blog/do-repeat-yourself/
6•max_sendfeld•12h ago•0 comments

Show HN: Sutra-OS – A self-hosted ontology platform

https://github.com/0nelight/sutra-os
14•0nelight•1h ago•2 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
200•Bender•11h ago•138 comments

My Quest to push native Three.js quality match AAA Game Engines

https://ben3d.ca/blog/building-the-aaa-lighting-pipeline-in-threejs
81•bhouston•3h ago•31 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
290•sammatilda•12h ago•114 comments

How to Intercept HTTP/3 Traffic: QUIC and Qpack

https://interceptsuite.com/blog/intercept-http3-traffic-quic-qpack-explained/
53•anof-cyber•5h ago•4 comments

Michael Mann's 'Heat' Copyright Fight Turns on a Deal with Himself

https://copyrightlately.com/michael-mann-heat-copyright-termination/
83•speckx•6h ago•37 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
98•maufl•6h ago•47 comments

Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings

http://groundworkcollaborative.org/news/amazons-decoy-deals-groundwork-investigation-reveals-near...
818•DeepLogin•10h ago•495 comments

Jolt – Clojure that speaks C

https://jolt-lang.net/
91•michaelsbradley•8h ago•28 comments

Strengthening the fight against online child sexual abuse

https://openai.com/index/strengthening-online-child-safety/
99•rossant•6h ago•216 comments

US will say "no" to global ban on killer robots

https://www.newsweek.com/us-expected-to-block-killer-robot-treaty-talks-12722369
54•madihaa•1h ago•54 comments
Open in hackernews

LLM-D: Kubernetes-Native Distributed Inference

https://llm-d.ai/blog/llm-d-announce
120•smarterclayton•1y ago

Comments

anttiharju•1y ago
I wonder if this is preferable to kServe
smarterclayton•1y ago
llm-d would make sense if you are running a very large production LLM serving setup - say 5+ full H100 hosts. The aim is to be much more focused than kserve is on exactly the needs of serving LLMs. It would of course be possible to run alongside kserve, but the user we are targeting is not typically a kserve deployer today.
anttiharju•1y ago
Do you think https://github.com/openai/CLIP can be ran on it? LLM makes me think of chatbots but I suppose because it's inference-based it would work. Somewhat unclear on what's the difference between LLMs and inference, I think inference is the type of compute LLMs use.

I wonder if inference-d would be a fitting name.

smarterclayton•1y ago
Inference is the process of evaluating a model ("inferring" a response to the inputs). LLMs are uniquely difficult to serve because they push the limits on the hardware.

The models we support come from the model server vLLM https://docs.vllm.ai/en/latest/models/supported_models.html, which has a focus on large generative models. I don't see CLIP in the list.

dzr0001•1y ago
I did a quick scan of the repo and didn't see any reference to Ray. Would this indicate that llm-d lacks support for pipeline parallelism?
qntty•1y ago
I believe this is a question you should ask about vLLM, not llm-d. It looks like vLLM does support pipeline parallelism via Ray: https://docs.vllm.ai/en/latest/serving/distributed_serving.h...

This project appears to make use of both vLLM and Inference Gateway (an official Kubernetes extension to the Gateway resource). The contributions of llm-d itself seems to mostly be a scheduling algorithm for load balancing across vLLM instances.

smarterclayton•1y ago
We inherit any multi-host support from vLLM, so https://docs.vllm.ai/en/latest/serving/distributed_serving.h... would be the expected path.

We plan to publish examples of multi-host inference that leverages LeaderWorkerSets - https://github.com/kubernetes-sigs/lws - which helps run ranked serving workloads across hosts. LeaderWorkerSet is how Google supports both TPU and GPU multi-host deployments - see https://github.com/kubernetes-sigs/lws/blob/main/config/samp... for an example.

Edit: Here is an example Kubernetes configuration running DeepSeek-R1 on vLLM multi-host using LeaderWorkerSet https://github.com/kubernetes-sigs/wg-serving/blob/main/serv.... This work would be integrated into llm-d.

rdli•1y ago
This is really interesting. For SOTA inference systems, I've seen two general approaches:

* The "stack-centric" approach such as vLLM production stack, AIBrix, etc. These set up an entire inference stack for you including KV cache, routing, etc.

* The "pipeline-centric" approach such as NVidia Dynamo, Ray, BentoML. These give you more of an SDK so you can define inference pipelines that you can then deploy on your specific hardware.

It seems like LLM-d is the former. Is that right? What prompted you to go down that direction, instead of the direction of Dynamo?

qntty•1y ago
It sounds like you might be confusing different parts of the stack. NVIDIA Dynamo for example supports vLLM as the inference engine. I think you should think of something like vLLM as more akin to GUnicorn, and llm-d as an application load balancer. And I guess something like NVIDIA Dynamo would be like Django.
smarterclayton•1y ago
llm-d is intended to be three clean layers:

1. Balance / schedule incoming requests to the right backend

2. Model server replicas that can run on multiple hardware topologies

3. Prefix caching hierarchy with well-tested variants for different use cases

So it's a 3-tier architecture. The biggest difference with Dynamo is that llm-d is using the inference gateway extension - https://github.com/kubernetes-sigs/gateway-api-inference-ext... - which brings Kubernetes owned APIs for managing model routing, request priority and flow control, LoRA support etc.

rdli•1y ago
I would think that that the NVidia Dynamo SDK (pipelines) is a big difference as well (https://github.com/ai-dynamo/dynamo/tree/main/deploy/sdk/doc...), or am I missing something?
Kemschumam•1y ago
What would be the benefit of this project over hosting VLLM in Ray?
smarterclayton•1y ago
That's a good example - I can at least answer about why it's a difference: different target user.

As I understand the Dynamo SDK it is about simplifying and helping someone get started with Dynamo on Kubernetes.

From the user set we work with (large inference deployers) that is not a high priority - they already have mature deployment opinions or a set of tools that would not compose well with something like the Dynamo SDK. Their comfort level with Kubernetes is moderate to high - either they use Kubernetes for high scale training and batch, or they are deploying to many different providers in order to get enough capacity and need a standard orchestration solution.

llm-d focuses on helping achieve efficiency dynamically at runtime based on changing traffic or workload on Kubernetes - some of the things the Dynamo SDK encodes are static and upfront and would conflict with that objective. Also, large deployers with serving typically have significant batch and training and they are looking to maximize capacity use without impacting their prod serving. That requires the orchestrator to know about both workloads at some level - which Dynamo SDK would make more difficult.

rdli•1y ago
In this analogy, Dynamo is most definitely not like Django. It includes inference aware routing, KV caching, etc. -- all the stuff you would need to run a modern SOTA inference stack.
qntty•1y ago
You're right, I was confusing TensorRT with Dynamo. It looks like the relationship between Dynamo and vLLM is actually the opposite of what I was thinking -- Dynamo can use vLLM as a backend rather than vice versa.