# @everywhere takes a very long time when using a cluster

**URL:** <https://discourse.julialang.org/t/everywhere-takes-a-very-long-time-when-using-a-cluster/35724>\
**Category:** General Usage\
**Created:** [March 8, 2020, 5:27pm UTC](https://discourse.julialang.org/t/everywhere-takes-a-very-long-time-when-using-a-cluster/35724 "2020-03-08T17:27:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pfarndt](https://avatars.discourse-cdn.com/v4/letter/p/8dc957/32.png) [@pfarndt](https://discourse.julialang.org/u/pfarndt)\
**Post date:** [March 9, 2020, 8:27am UTC](https://discourse.julialang.org/t/everywhere-takes-a-very-long-time-when-using-a-cluster/35724/3 "2020-03-09T08:27:00Z")

</div>

I raised a similar (probably the same) issue here:

> [@Module loading on workers](https://discourse.julialang.org/t/module-loading-on-workers/31814):
>
> Through some trials and errors I realized that modules, which are loaded with using, are also loaded on the already existing workers. Therefore the following code runs without an error: using Distributed addprocs(2) using PyPlot pmap(workers()) do w w, myid(), PyPlot.version end I find this behavior quite inconvenient because in a situation with many workers (to generate some data) connected to one jupyter notebook kernel (to analyze this data) I rather prefer not to load a plotting packa…

I am still not satisfied with the current situation but now know how to avoid the greatest pitfalls, e.g. first load all the packages you need on the master, then add workers, then load packages you definitely need at workers.

---

_[View the full topic](https://discourse.julialang.org/t/everywhere-takes-a-very-long-time-when-using-a-cluster/35724)._