tatef
Joined 6 years ago
Joined 6 years ago
I’m also a big local model enthusiast, but the truth is I don’t believe people should have to binary switch between a local setup and OpenAI/Anthropic.
So instead of making it about hosted vs local, I decided to build a tool which allows Claude Code or Codex to delegate work to subagents running locally on your machine (or network) OR via other provider (OpenRouter).
This is different from the typical subagents you can spin up which will contribute to your usage quota/token costs. It also means you can put your GPU to use for simpler tasks instead of letting Claude burn usage on less important work.
Check it out here: https://github.com/labscommunity/yeschef
Open to feedback :)
To get it functioning, we split models into shards and pre-compiled them to OpenVINO IR graphs.
Since then, we’ve been working on a lot of optimizations to make sharding and running models on Intel much more performant. Most of our initial improvements are thanks to the use of speculative decoding (with some interesting workarounds there) and also micro-batching and continuous batching to improve the total throughput.
We’re still in the early days, but from our work so far:
- We ran an 8B parameter model on two Intel PCs, serving two users concurrently via iGPUs at ~43 tok/s aggregate - After adding an additional PC and user, it reached 64.67 tok/s - We’ve successfully sharded larger models (e.g. with 70B parameters), and with Cascadia inference was 3.1x faster than basic sharding - And for fun, we got 39 Intel AI PCs, hooked them up via ethernet, and sharded a 70B model across them. Benchmarks aren’t super impressive yet (~1 tok/s on CPU), but we’ve been making a ton of progress there.
If you’re wondering why we’re doing this, there’s a few reasons. There is a lot of Intel hardware out there, and dedicated AI hardware right now is expensive.
Organizations that own Intel computers will be able to pool their computing power to run models locally. For hobbyists with Intel GPU rigs or Intel Xeon Server PCs, you likely want inference to be optimized for your hardware. Cascadia is aiming to be a runtime for anyone wanting to run AI on Intel hardware and squeeze the most juice out of their machines.
Cascadia is open source (Apache 2.0) and available now.
This is alpha, so we’re open to any feedback on the architecture.
Give it a go and let us know what you think :)
Coming to you today with Autolab, a framework I built that combines Ralph loops and Karpathy's autoresearch to design and run tests and make novel research discoveries. I hope one day a similar framework can be used with hardware, but for now, I've been using this tool in my workflows and find it incredibly useful. Wanted to share.
Wanted to share a project I've been working on aimed at helping solve the context problem called Memoryport. It works across LLM providers/apps, stores conversations locally, is fully OSS, and enables anyone to keep track of their memories over time. I tested mine with 500M tokens of context space (note: not the same as a context window) and only added ~300ms of latency to the inference session. I also built out an open spec called AMP that standardizes the communication protocol for how memory systems should interact with LLMs (see repo).
More than happy to answer any questions and hope you all find this as useful as I have.
There is no writing to SSDs on inference with this architecture.