Update README.md

50d5e948f8846662a9f770df13f41c5853bd265a · 2024-07-16 02:40:50 -0700 · Alex Cheema

Files touched

M README.md

Diff

commit 50d5e948f8846662a9f770df13f41c5853bd265a
Author: Alex Cheema <41707476+AlexCheema@users.noreply.github.com>
Date:   Tue Jul 16 02:40:50 2024 -0700

    Update README.md
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 59cec1f4..5653b2e9 100644
--- a/README.md
+++ b/README.md
@@ -49,7 +49,7 @@ exo provides a ChatGPT-compatible API for running models. It's a one-line change
 
 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](topology/ring_memory_weighted_partitioning.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 to split up a model across devices. The default partitioning strategy is [ring memory weighted partitioning](exo/topology/ring_memory_weighted_partitioning.py). This runs an inference in a ring where each device runs a number of model layers proportional to the memory of the device.
 
 <picture>
   <img alt="ring topology" src="docs/ring-topology.png" width="30%" height="30%">

← b6d91972 add notice of python>=3.12.0 · back to Exo · Typo ring memory weighted partitioning strategy b897fa44 →