kcorbitt

Joined 13 years ago

Karma
6,257
Submissions
745
Member since
Mar 6
Hi, my name is Kyle Corbitt.

Currently I'm working on openpipe.ai. Previously worked at YC and Google.

personal site: corbt.com email: kyle@ above. I respond to emails.

View on Hacker News

Recent submissions

Comment · 8 months ago
And lately, the sweet spot has been moving upwards every 6-8 weeks with the model release cycle.
Comment · 9 months ago
Is it?
Comment · 1 year ago
Dang, hadn't seen that. Namespace collision strikes again.
Comment · 1 year ago
I really like RLPR for when you have a known-good answer to compare to as well!
Comment · 1 year ago
No, we don't do anything. Theoretically we could judge several times with different ordering.

We could measure order bias really easily though; we just need to look at the average score by rollout position across many runs. I'll add that to my list of experiments!

Comment · 1 year ago
Thank! If there are any topics that you'd find particularly interesting, let me know and I can try to find time. :)
Comment · 1 year ago
Looks cool! With vLLM v1, prefix caching is enabled by default and seems quite performant. Is the advantage of LMCache the fact that you can offload to CPU and disk as well? How much is throughput/latency affected if you need to pull a large KV cache from disk/cpu instead of GPU RAM?

Also, how realistic would it be to share the KV cache across vllm nodes within a data center? It would be really nice to be able to freely distribute requests to a pool of vLLM workers without worrying about prefix-aware routing, but maybe that isn't the right approach because moving the KV cache around would be too slow?

Comment · 1 year ago
Comment · 1 year ago
The real answer is that nobody trusts their automated evals enough to be confident that any given automatically-trained release actually improves performance, even if eval scores go up. So for now everyone batches up updates and vibe-checks them before rolling them out.
Comment · 1 year ago
It seems like the speedups here are most useful for small models, since on larger models a smaller fraction of the total time would be spent swapping between kernels? Would be interesting to see at least theoretical results for LLMs in the 14-70B parameter range, which is what most folks deploy in practice.

And of course the effect on throughput at larger batch sizes, which they allude to at the end.

Overall a very interesting result!

Comment · 1 year ago
There are many industries where you need lots of experience before you're a net contributor to productivity. This is true for everything from hairdressers to doctors. We have ways of dealing with this (eg. taking out loans to undergo years of training).

The problem comes if the number of years of experience you need to outperform the frontier AI models advances at more than 1 per year, which is not out of the question.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton