1
0

在家中使用日常设备运行自己的 AI 集群。由 exo labs 维护。

Alex Cheema bde1e53f5f add license 9 сар өмнө
docs 231cde5ff5 ring topology image 9 сар өмнө
examples 1d5c28aed4 (partially) restore exo node equality by forwarding prompts to the dynamically selected head 9 сар өмнө
exo dd8d18128c add an opaque inference_state that inference engines can use to pass around small state to other devices 9 сар өмнө
.gitignore 850b72d3ea make StatefulShardedModel callable, add some tests for mlx sharded inference 9 сар өмнө
LICENSE bde1e53f5f add license 9 сар өмнө
README.md ed7672e32c Update README.md 9 сар өмнө
main.py dd8d18128c add an opaque inference_state that inference engines can use to pass around small state to other devices 9 сар өмнө
main_static.py 32f2e36fd3 main rename 9 сар өмнө
requirements.txt bf565f945d fix #7 no module named aiohttp 9 сар өмнө

README.md

exo logo exo: Run your own AI cluster at home with everyday devices. Maintained by [exo labs](https://x.com/exolabs_).

[Discord](https://discord.gg/EUnjGpsmWw) | [Telegram](https://t.me/+Kh-KqHTzFYg3MGNk) | [X](https://x.com/exolabs_)


Forget expensive NVIDIA GPUs, unify your existing devices into one powerful GPU: iPhone, iPad, Android, Mac, Linux, pretty much any device!

Get Involved

exo is experimental software. Expect bugs early on. Create issues so they can be fixed. The exo labs team will strive to resolve issues quickly.

We also welcome contributions from the community. We have a list of bounties in this sheet.

Features

Wide Model Support

exo supports LLaMA and other popular models.

Dynamic Model Partitioning

exo optimally splits up models based on the current network topology and device resources available. This enables you to run larger models than you would be able to on any single device.

Automatic Device Discovery

exo will automatically discover other devices using the best method available. Zero manual configuration.

ChatGPT-compatible API

exo provides a ChatGPT-compatible API for running models. It's a one-line change in your application to run models on your own hardware using exo.

Device Equality

Unlike other distributed inference frameworks, exo does not use a master-worker architecture. Instead, exo devices connect p2p. As long as a device is connected somewhere in the network, it can be used to run models.

Exo supports different partitioning strategies to split up a model across devices. The default partitioning strategy is ring memory weighted partitioning. This runs an inference in a ring where each device runs a number of model layers proportional to the memory of the device.

ring topology

Installation

The current recommended way to install exo is from source.

From source

Python>=3.12.0 is required because of issues with asyncio in previous versions.

git clone https://github.com/exo-explore/exo.git
cd exo
pip install -r requirements.txt

Documentation

Example Usage on Multiple MacOS Devices

Device 1:

python3 main.py

Device 2:

python3 main.py

That's it! No configuration required - exo will automatically discover the other device(s).

The native way to access models running on exo is using the exo library with peer handles. See how in this example for Llama 3.

exo also starts a ChatGPT-compatible API endpoint on http://localhost:8000. Note: this is currently only supported by tail nodes (i.e. nodes selected to be at the end of the ring topology). Example request:

curl http://localhost:8000/v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{
     "model": "llama-3-70b",
     "messages": [{"role": "user", "content": "What is the meaning of exo?"}],
     "temperature": 0.7
   }'
curl -X POST http://localhost:8001/api/v1/chat -H "Content-Type: application/json" -d '{"messages": [{"role": "user", "content": "What is the meaning of life?"}]}'

Inference Engines

exo supports the following inference engines:

Networking Modules

Known Issues

  • 🚧 As the library is evolving so quickly, the iOS implementation has fallen behind Python. This is being worked on, and longer term we will push out an approach that will unify the implementations so we don't have to maintain separate implementations.