# @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:** 9

<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: [November 26, 2020, 8:50pm UTC](https://discourse.julialang.org/t/everywhere-takes-a-very-long-time-when-using-a-cluster/35724/9 "2020-11-26T20:50:01Z")

</div>

ok - nowadays I usually take a `ElasticManager` to manage my workers and tweak the `Worker connect command` (see on the linked page) such that all the packages are all loaded before `ClusterManagers.elastic_worker(...)` is called. Depending on how you start your workers this is more gentle on the filesystem. I guess all this loading takes so long because all of a sudden several nodes (in my case 100+) want to load stuff (precompiled or not) from some files.

[https://juliahub.com/docs/ClusterManagers/2gedf/0.4.0/#Using--ElasticManager--dynamically-adding-workers-to-a-cluster](https://juliahub.com/docs/ClusterManagers/2gedf/0.4.0/#Using--ElasticManager--dynamically-adding-workers-to-a-cluster)

---

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