Viewing profile — smarterclayton
smarterclayton
HN member- Joined
- Mon, Mar 30, 2015, 2:31 PM UTC
- HN karma
- 533
- Public activity
- 199 items
- HN profile
- View on Hacker News ↗
About smarterclayton
No profile information was provided.
Recent public activity
-
comment
Comment #45053309
A good rule of thumb is that a prefill token is about 1/6th the compute cost of decode token, and that you can get about 15k prefill tokens a second on Llama3 8B on a single H100. …
-
comment
Comment #44043862
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 sta…
-
comment
Comment #44043502
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. Pr…
-
comment
Comment #44043121
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-hos…
-
comment
Comment #44042865
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…
-
comment
Comment #44042496
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…
- story
-
comment
Comment #41135188
CPU tracking is provided by the metrics API, which either reads kubelet metrics directly (the original, old, but simplest way), or a metrics adapter that reads the metrics from a t…
-
comment
Comment #40671877
Pretty well. Anthropic runs some of Claude inference on GKE and TPU v5e - this talk at the last GCP conference has some details: https://youtu.be/b87I1plPeMg?si=T4XSFUzXG8BwpphR Ec…
-
comment
Comment #39454863
There is a lot of work to make the actual infrastructure and lower level management of lots and lots of GPUs/TPUs open as well - my team focuses on making the infrastructure bit at…
-
comment
Comment #38879733
As an aside: This principle (always shutdown uncleanly) was a significant point of design discussion in Kubernetes, another one of the projects that adapted lessons learned inside …
- story
-
comment
Comment #38546125
From the report: "As part of the evaluation process, on a popular benchmark, HellaSwag (Zellers et al., 2019), we find that an additional hundred finetuning steps on specific websi…
-
comment
Comment #38226042
True. The pod’s monotonic and atomic lifecycle across containers is a significant difference, but you can broadly accomplish similar behaviors with an alloc for sharing resources.
-
comment
Comment #38224552
I will note that a trend I have observed with recent ML - as we increasingly use accelerators and models correspondingly grow in size, we are returning to a "one machine, one workl…
-
comment
Comment #38224503
Also, I should point out that a set of machines hosting TPUs is referred to as a "pod", which is not the same thing as a Kubernetes pod (also referenced in this doc). The term "pod…
-
comment
Comment #38223979
Disclaimer: work associated with this team, didn't write or review the blog post Article stated that it was throughput scheduling the pods on the clusters (from unrelated benchmark…
-
comment
Comment #37070526
Our bottleneck was serialization of objects to bytes to send to etcd. Etcd cpu should be about 0.01-0.001 control plane CPU, and control plane apiserver CPU has been dominated by s…
-
comment
Comment #37069418
That’s fair - as the perpetrator of much of that abstraction I believe that highlighting the type system aspect of this code obscures the real problem we were solving for, which Go…
-
comment
Comment #37069253
I have a lot of respect for Kris but in this context, as the person who approved the PR adding the “Object” interface to the code base (and participated in most of the subsequent d…
-
comment
Comment #37068213
> kubernetes went ahead and implemented an oop system in golang I don’t think this was ever an objective, can you clarify what you mean by “oop system” and where we implemented it?…
-
comment
Comment #36674074
Agreed that is a feature and not a bug. But! The one thing that custom orchestrators can’t do is easily get the benefit of kubelet isolation of containers and resource management. …
-
comment
Comment #36674032
In general, the intent here is to leave open room for just that. dependsOn was proposed during the kep review but deferred. But because init containers and regular containers share…
-
comment
Comment #36674008
The challenge with a separate attribute is that it is not forward compatible with new features we might add to pods around ordering and lifecycle. If we used a simple boolean, even…
-
comment
Comment #36666359
We did that to leave open more complex ordering of both init containers and sidecars (regular containers do not have a restart order). For instance, you might have a service mesh t…