# Multi-threaded worker processes

**URL:** https://discourse.julialang.org/t/multi-threaded-worker-processes/33034
**Category:** General Usage
**Created:** [January 6, 2020, 5:03pm UTC](https://discourse.julialang.org/t/multi-threaded-worker-processes/33034 "2020-01-06T17:03:38Z")
**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: [January 7, 2020, 8:01am UTC](https://discourse.julialang.org/t/multi-threaded-worker-processes/33034/4 "2020-01-07T08:01:02Z")

</div>

Related:

[https://github.com/JuliaLang/julia/issues/17887](https://github.com/JuliaLang/julia/issues/17887)

FYI, as Transducers.jl has thread- and Distributed.jl-based parallelisms with a common interface (ref: [Thread- and process-based parallelisms in Transducers.jl (+ some news)](https://discourse.julialang.org/t/thread-and-process-based-parallelisms-in-transducers-jl-some-news/32285)), it should not be too hard to stitch things together to use thread-based reduction inside Distributed.jl-based reduction. This would then automatically give us a superset of `pmap` that supports other processings like filtering to be fused with mapping.

---

_[View the full topic](https://discourse.julialang.org/t/multi-threaded-worker-processes/33034)._