# Is splitting the Julia code into smaller scripts impacting performance?

**URL:** <https://discourse.julialang.org/t/is-splitting-the-julia-code-into-smaller-scripts-impacting-performance/103613>\
**Category:** Performance\
**Created:** [September 7, 2023, 2:52pm UTC](https://discourse.julialang.org/t/is-splitting-the-julia-code-into-smaller-scripts-impacting-performance/103613 "2023-09-07T14:52:30Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [September 7, 2023, 2:59pm UTC](https://discourse.julialang.org/t/is-splitting-the-julia-code-into-smaller-scripts-impacting-performance/103613/2 "2023-09-07T14:59:17Z")

</div>

> [@CrisCool](#):
>
> Would my many include() calls impact performance in the the two cases above?

It should have a negligible impact (compared with simply pasting all of the code into a single file).

However, if you are writing re-usable code, I would strongly encourage you to think about putting the re-usable pieces into modules/packages, rather than thinking of it as “scripts”. (And write callable functions, not runnable scripts.) See also [Best practise: organising code in Julia - #2 by stevengj](https://discourse.julialang.org/t/best-practise-organising-code-in-julia/74362/2)

---

_[View the full topic](https://discourse.julialang.org/t/is-splitting-the-julia-code-into-smaller-scripts-impacting-performance/103613)._