# RemoteChannels and workload queue architecture

**URL:** <https://discourse.julialang.org/t/remotechannels-and-workload-queue-architecture/18056>\
**Category:** General Usage\
**Tags:** parallel\
**Created:** [November 27, 2018, 11:26am UTC](https://discourse.julialang.org/t/remotechannels-and-workload-queue-architecture/18056 "2018-11-27T11:26:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![draftman9](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/draftman9/32/38128_2.png) [@draftman9](https://discourse.julialang.org/u/draftman9)\
**Post date:** [October 14, 2024, 2:34am UTC](https://discourse.julialang.org/t/remotechannels-and-workload-queue-architecture/18056/2 "2024-10-14T02:34:00Z")

</div>

Nice idea! I just realized a prototype these days, which works well on the cluster. I have searched all the internet, but I did not find any existing packages about this. I want to develop and release a corresponding package. It will allocate all nodes (cross nodes, all available local and remote CPU cores) on the cluster to execute the tasks in the 'requests` (RemoteChannel). Very relative to your idea. If you (or any viewer) are interested in it, we can cooperate to develop this useful package to fill the hole of julia parallel computation for clusters.

---

_[View the full topic](https://discourse.julialang.org/t/remotechannels-and-workload-queue-architecture/18056)._