# First call latency in distributed code

**URL:** https://discourse.julialang.org/t/first-call-latency-in-distributed-code/88917
**Category:** Performance
**Tags:** distributed, latency
**Created:** [October 18, 2022, 3:07pm UTC](https://discourse.julialang.org/t/first-call-latency-in-distributed-code/88917 "2022-10-18T15:07:32Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![jmair](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jmair/32/35117_2.png) [@jmair](https://discourse.julialang.org/u/jmair)
#### Post date: [October 19, 2022, 11:06am UTC](https://discourse.julialang.org/t/first-call-latency-in-distributed-code/88917/19 "2022-10-19T11:06:39Z")

</div>

It is definitely worth upgrading to `v1.8+`. You don’t need to compile it yourself from source on the cluster (but this is what I do), but I think the below will work:

```nohighlight
cd ~
wget https://julialang-s3.julialang.org/bin/linux/x64/1.8/julia-1.8.2-linux-x86_64.tar.gz
tar -xvf julia-1.8.2-linux-x86_64.tar.gz
echo "alias julia=~/julia-1.8.2/bin/julia" >> ~/.bashrc

```

This means that when you type `julia` in bash, it will redirect it to the right executable. You may want to remove any `module load`s for julia if you are using environment files.

p.s. You can of course change the version to the one you want.

---

_[View the full topic](https://discourse.julialang.org/t/first-call-latency-in-distributed-code/88917)._