.rst .pdf

repository open issue suggest edit

Task Design Patterns

This section is a collection of common design patterns (and anti-patterns) for Ray tasks. It is meant as a handbook for both:

• New users trying to understand how to get started with Ray, and

• Advanced users trying to optimize their use of Ray tasks

You may also be interested in visiting the design patterns section for actors.

• Pattern: Tree of tasks
  • Example use case
  • Code example
• Pattern: Map and reduce
  • Example use case
  • Code examples
• Pattern: Using ray.wait to limit the number of in-flight tasks
  • Example use case
  • Code example
• Pattern: Using generators to reduce heap memory usage
  • Example use case
  • Code example
• Antipattern: Closure capture of large / unserializable object
  • Code example
• Antipattern: Too fine-grained tasks
  • Code example
• Antipattern: Accessing Global Variable in Tasks/Actors
  • Code example
  • Notes
• Antipattern: Calling ray.get in a loop
  • Code example
• Antipattern: Processing results in submission order using ray.get
  • Code example
• Antipattern: Fetching too many results at once with ray.get
  • Code example
• Antipattern: Redefining task or actor in loop
  • Code example
• Antipattern: Unnecessary call of ray.get in a task
  • Notes
  • Code example

previous

Scheduling

next

Pattern: Tree of tasks