# Example for the Depth first multithread implementation performance gain as a motivation

**URL:** https://discourse.julialang.org/t/example-for-the-depth-first-multithread-implementation-performance-gain-as-a-motivation/32328
**Category:** Performance
**Tags:** question, proposal
**Created:** [December 16, 2019, 10:39am UTC](https://discourse.julialang.org/t/example-for-the-depth-first-multithread-implementation-performance-gain-as-a-motivation/32328 "2019-12-16T10:39:29Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)
#### Post date: [December 16, 2019, 3:12pm UTC](https://discourse.julialang.org/t/example-for-the-depth-first-multithread-implementation-performance-gain-as-a-motivation/32328/4 "2019-12-16T15:12:57Z")

</div>

Early termination in the parallel `reduce` I implemented in Transducers.jl depends on the depth-first scheduler. Ref: [Thread- and process-based parallelisms in Transducers.jl (+ some news) - #3 by tkf](https://discourse.julialang.org/t/thread-and-process-based-parallelisms-in-transducers-jl-some-news/32285/3)

---

_[View the full topic](https://discourse.julialang.org/t/example-for-the-depth-first-multithread-implementation-performance-gain-as-a-motivation/32328)._