News for hackers. Stuff that matters.
Re:Eager Execution: An imperative, define-by-run interface t... by josh11b on Tuesday October 31, 2017 @02:18PM (#15595299)
I'm on the team that worked on this -- happy to answer questions!
Re:Eager Execution: An imperative, define-by-run interface t... by gormanc on Tuesday October 31, 2017 @08:31PM (#15597985)
Hot damn this has got me all giddy. How will this work on single node multi-GPU systems? For example, with PyTorch you have to either use threading, multiprocessing, or even MPI. Can you think of a not-too-scary way to use eager execution with multiple GPUs?
Re:Eager Execution: An imperative, define-by-run interface t... by alextp on Tuesday October 31, 2017 @10:21PM (#15598435)
We're still fairly early in the project, so for now threading is the only supported way.

We can do better, however, and we're working on ways to leverage the hardware better (for example, if you have no data-dependent choices in your model we can enqueue kernels in parallel on all GPUs in your machine at once from a single python thread, which will perform much better than explicit python multithreading).

Stay on the lookout as we release new experimental APIs to leverage multiple GPUs and multiple machines.