# How to improve REPL startup time OR clear the workspace

**URL:** <https://discourse.julialang.org/t/how-to-improve-repl-startup-time-or-clear-the-workspace/104171>\
**Category:** Performance\
**Created:** [September 23, 2023, 3:33am UTC](https://discourse.julialang.org/t/how-to-improve-repl-startup-time-or-clear-the-workspace/104171 "2023-09-23T03:33:00Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![abraemer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/abraemer/32/51403_2.png) [@abraemer](https://discourse.julialang.org/u/abraemer)\
**Post date:** [September 23, 2023, 5:38am UTC](https://discourse.julialang.org/t/how-to-improve-repl-startup-time-or-clear-the-workspace/104171/3 "2023-09-23T05:38:01Z")

</div>

So just like @brianguenter I reccomend [using Revise.jl](https://docs.julialang.org/en/v1/manual/workflow-tips/#Revise-based-workflows) as it will keep source and REPL state in sync. However there are [some limitations](https://timholy.github.io/Revise.jl/stable/limitations/) such as struct/const redefinitions that Revise can’t handle. If you find yourself changing struct definitions often, there are some work-arounds (read [here](https://discourse.julialang.org/t/thoughts-and-tempering-expectations-on-redefining-structs/101190) for more info on background and work-arounds). Or you can use Pluto.jl for prototyping and interactivity. I personally do all my exploration/research/drafting packages in Pluto.jl and then switch over to a Revise-based workflow when creating a package.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-improve-repl-startup-time-or-clear-the-workspace/104171)._