# Julia in Colab

**URL:** <https://discourse.julialang.org/t/julia-in-colab/126600>\
**Category:** General Usage\
**Tags:** colab\
**Created:** [March 5, 2025, 10:55pm UTC](https://discourse.julialang.org/t/julia-in-colab/126600 "2025-03-05T22:55:11Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![vchuravy](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/vchuravy/32/8_2.png) [@vchuravy](https://discourse.julialang.org/u/vchuravy)\
**Post date:** [March 8, 2025, 2:31pm UTC](https://discourse.julialang.org/t/julia-in-colab/126600/25 "2025-03-08T14:31:24Z")

</div>

@metrizable I noticed that Collab comes with a pre-populated default environment. We discourage that for many reasons, partly because it leads to unfortunate interactions when users want to install their own packages.

[Admin: How to provide Julia to users?](https://juliahpc.github.io/sysadmin_julia/) has some more information on that topic (HPC admins also have the initial desire to provide a pre-populated default environment)

I noticed that precompilation times are quite bad, the machines seem to be beefy enough so I wonder if the slow down is some unfortunate interaction with the file system?

Ideally one would be able to have a transparent cache for JULIA\_DEPOT\_PATH. (`~/.julia`) (That’s something we do on GitHub actions), and support for Project.toml?

---

_[View the full topic](https://discourse.julialang.org/t/julia-in-colab/126600)._