[object Object]

← back to Exo

reference the code for each feature listed in README

1b194b43f6a3f31f2112a2958376a3649959cf1a · 2024-07-18 16:18:01 -0700 · Alex Cheema

Files touched

Diff

commit 1b194b43f6a3f31f2112a2958376a3649959cf1a
Author: Alex Cheema <alexcheema123@gmail.com>
Date:   Thu Jul 18 16:18:01 2024 -0700

    reference the code for each feature listed in README
---
 README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index d81e7bd1..f947d5f0 100644
--- a/README.md
+++ b/README.md
@@ -33,25 +33,25 @@ We also welcome contributions from the community. We have a list of bounties in
 
 ### Wide Model Support
 
-exo supports LLaMA and other popular models.
+exo supports LLaMA ([MLX](exo/inference/mlx/models/sharded_llama.py) and [tinygrad](exo/inference/tinygrad/models/llama.py)) 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.
+exo [optimally splits up models](exo/topology/ring_memory_weighted_partitioning_strategy.py) 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.
+exo will [automatically discover](https://github.com/exo-explore/exo/blob/945f90f676182a751d2ad7bcf20987ab7fe0181e/exo/orchestration/standard_node.py#L154) 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.
+exo provides a [ChatGPT-compatible API](exo/api/chatgpt_api.py) for running models. It's a [one-line change](examples/chatgpt_api.py) 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.
+Unlike other distributed inference frameworks, exo does not use a master-worker architecture. Instead, exo devices [connect p2p](https://github.com/exo-explore/exo/blob/945f90f676182a751d2ad7bcf20987ab7fe0181e/exo/orchestration/standard_node.py#L161). 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](exo/topology/ring_memory_weighted_partitioning_strategy.py). This runs an inference in a ring where each device runs a number of model layers proportional to the memory of the device.
+Exo supports different [partitioning strategies](exo/topology/partitioning_strategy.py) to split up a model across devices. The default partitioning strategy is [ring memory weighted partitioning](exo/topology/ring_memory_weighted_partitioning_strategy.py). This runs an inference in a ring where each device runs a number of model layers proportional to the memory of the device.
 
 <p>
     <picture>

← 945f90f6 allow overriding inference_engine and separate flag for TINY  ·  back to Exo  ·  remove old PartitioningStrategy 0af164f0 →