# Starting GLMakie takes very long

**URL:** <https://discourse.julialang.org/t/starting-glmakie-takes-very-long/64106>\
**Category:** Performance\
**Tags:** makie\
**Created:** [July 5, 2021, 8:59pm UTC](https://discourse.julialang.org/t/starting-glmakie-takes-very-long/64106 "2021-07-05T20:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![TsurHerman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tsurherman/32/1234_2.png) [@TsurHerman](https://discourse.julialang.org/u/TsurHerman)\
**Post date:** [July 6, 2021, 7:48am UTC](https://discourse.julialang.org/t/starting-glmakie-takes-very-long/64106/10 "2021-07-06T07:48:52Z")

</div>

Take a look at

> [@\[ANN\] Fezzik.jl: build locally for better integration with VSCode](https://discourse.julialang.org/t/ann-fezzik-jl-build-locally-for-better-integration-with-vscode/63810):
>
> [Fezzik.jl](https://github.com/TsurHerman/Fezzik) simplifies the process of building custom sys images, Without a custom sysimg , working with Julia and going through the same jitting over and over again is a pain. However up until now the default brute\_build\_julia() would replace the original sysimg with the newly minted one. Recently it became un-stable for me because VSCode(VSCodeServer.jl) which is my main IDE for Julia, keeps crashing when not seeing the original sysimg. The up-side of VScode Julia is that it can use a custom …

if you use VSCode as your IDE then  
`brute_build_local()`  
is what you need, otherwise you can use  
`brute_build_julia()`  
to replace the original sysimg(system image - the compiled code loaded at startup)  
but it is more likely to mess-up your julia installation(in that case you’ll have to re-install julia).

---

_[View the full topic](https://discourse.julialang.org/t/starting-glmakie-takes-very-long/64106)._