* Revert "Make tests more informative (#372)" This reverts commitfd353250c8. * fix bugs, in particular deactivate worker service on driver and remove condition variables * changes to minimize the changes in this PR * switch from faulty mutex synchronization to using atomics * Increase the default size of the message queues, to accommodate exporting large numbers of remote functions. This is a temporary fix, but not a long term solution. * Reorganize the scheduler export code to queue up exports. This does not solve the underlying problem yet, but sets up a solution. * Start a separate thread on driver to print error messages by constantly querying the scheduler. This is a temporary solution because the solution based on starting a worker service for the driver which the scheduler can push error messages to is buggy. * Fix segfault in taskcapsule destructor. * Move tests for catching errors into a separate test file. * Revert "roll back grpc (#368)" This reverts commitc01ef95d04.
Ray
Ray is an experimental distributed extension of Python. It is under development and not ready for general use.
The goal of Ray is to make it easy to write machine learning applications that run on a cluster while providing the development and debugging experience of working on a single machine.
Before jumping into the details, here's a simple Python example for doing a Monte Carlo estimation of pi (using multiple cores or potentially multiple machines).
import ray
import numpy as np
# Start a scheduler, an object store, and some workers.
ray.init(start_ray_local=True, num_workers=10)
# Define a remote function for estimating pi.
@ray.remote([int], [float])
def estimate_pi(n):
x = np.random.uniform(size=n)
y = np.random.uniform(size=n)
return 4 * np.mean(x ** 2 + y ** 2 < 1)
# Launch 10 tasks, each of which estimates pi.
result_ids = []
for _ in range(10):
result_ids.append(estimate_pi.remote(100))
# Fetch the results of the tasks and print their average.
estimate = np.mean([ray.get(result_id) for result_id in result_ids])
print "Pi is approximately {}.".format(estimate)
Within the for loop, each call to estimate_pi.remote(100) sends a message to
the scheduler asking it to schedule the task of running estimate_pi with the
argument 100. This call returns right away without waiting for the actual
estimation of pi to take place. Instead of returning a float, it returns an
object ID, which represents the eventual output of the computation (this is
a similar to a Future).
The call to ray.get(result_id) takes an object ID and returns the actual
estimate of pi (waiting until the computation has finished if necessary).
Next Steps
- Installation on Ubuntu, Mac OS X, Windows, Docker
- Tutorial
- About the System
- Using Ray on a Cluster