Master / Slave Farming #1

New Issue

mike · 2020-01-02T09:27:48-08:00

mike commented

2020-01-02 09:27:48 -08:00

Because evolving can take much less PC resources than determining fitness, we could implement a system where Slave machines determine fitness for their population, then send their Chromosomes+Fitness back to the Master server for evolution, which then redistributes Chromosomes back to Slave machines afterward.

Example:

Master creates a population of 1000
Master sends 250 to each of four Slave machines
Slave machines each finish determining fitness via tests / simulations / whatever
Slave machines send Chromosomes+Fitness back to Master
Master waits to receive entire population from all Slave machines
Master performs evolution and records stats / champions / etc
Repeat to Step 2

Could configure different population splits to different machines, to account for different machine capabilities (ie: Send 900 Chromosomes to a fast machine and 100 to a slow machine).

Because evolving can take much less PC resources than determining fitness, we could implement a system where *Slave* machines determine fitness for their population, then send their Chromosomes+Fitness back to the *Master* server for evolution, which then redistributes Chromosomes back to *Slave* machines afterward. Example: 1. *Master* creates a population of 1000 2. *Master* sends 250 to each of four *Slave* machines 3. *Slave* machines each finish determining fitness via tests / simulations / whatever 4. *Slave* machines send Chromosomes+Fitness back to *Master* 5. *Master* waits to receive entire population from all *Slave* machines 6. *Master* performs evolution and records stats / champions / etc 7. Repeat to Step 2 Could configure different population splits to different machines, to account for different machine capabilities (ie: Send 900 Chromosomes to a fast machine and 100 to a slow machine).

mike added the

enhancement

label 2020-01-02 09:28:53 -08:00

Sign in to join this conversation.