
On Apr 3, 2007, at 12:13 PM, robomancer wrote:
Run phase: a "master" process assigns an experiment to each runner. When we get a result back, log the result to a file and send a new experiment to that runner. Repeat until all experiments are done.
As something quick & dirty... couldn't you just : a) have a postgres db on 1 machine and run a master on that. b) run slave nodes on all the other machines in reactor loops c) master installs commands / file data into postgres d) children poll postgres for commands, execute & log to pg as necessary its not elegant at all, but you could do that really really fast. you don't have to worry about nodes talking to one another - and they can be specifically assigned tasks. // Jonathan Vanasco | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | SyndiClick.com | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | FindMeOn.com - The cure for Multiple Web Personality Disorder | Web Identity Management and 3D Social Networking | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | RoadSound.com - Tools For Bands, Stuff For Fans | Collaborative Online Management And Syndication Tools | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -