I’m fairly new to julia, and not overly experienced with scaling to huge numbers of processes, so forgive me if I’m missing something obvious. Alright, to be honest, I actually used a couple thousand cpu-hours to run using DoubleFloats, but it looks like 1+2 would have done the same. From my testi…

I’ve hacked together a precompilation script here , which produces a sysimage with all the necessary Distributed code precompiled. This drastically reduces the time taken to call @everywhere 1+2. I’ve tested it on 100 processes, and the time goes down from ~70 seconds to ~2 seconds. If this scales…

Why does julia use thousands of cpu-hours to compute 1+2?

General Usage

moble August 8, 2021, 10:02pm 2

See also here and here.

Topic		Replies	Views
@everywhere takes a very long time when using a cluster General Usage	16	3032	February 11, 2022
First call latency in distributed code Performance distributed , latency	42	1087	October 21, 2022
Baffling addprocs() with @everywhere Julia at Scale	17	3443	April 24, 2018
Several questions on distributed computing from a beginner General Usage question , parallel-computing	21	552	May 28, 2024
Questions about getting started with parallel computing Julia at Scale	18	5778	June 22, 2019

Why does julia use thousands of cpu-hours to compute 1+2?

Related topics