# Large vs Small Packages
**URL:** https://discourse.julialang.org/t/large-vs-small-packages/9447
**Category:** General Usage
**Tags:** question
**Created:** [March 2, 2018, 9:47am UTC](https://discourse.julialang.org/t/large-vs-small-packages/9447 "2018-03-02T09:47:39Z")
**Posts on this page:** 3
**Page:** 2
### Author:  [@nsajko](https://discourse.julialang.org/u/nsajko)
#### Post date: [June 30, 2023, 12:59pm UTC](https://discourse.julialang.org/t/large-vs-small-packages/9447/21 "2023-06-30T12:59:05Z")
A middle ground between a monolithic package and splitting it up into several packages is splitting the big package’s code into several submodules.
---
### Author:  [@Elrod](https://discourse.julialang.org/u/Elrod)
#### Post date: [June 30, 2023, 8:25pm UTC](https://discourse.julialang.org/t/large-vs-small-packages/9447/22 "2023-06-30T20:25:33Z")
If you can break up a large package into many that do not depend on one another, that can speed up precompile times, as now they can precompile in parallel.
---
### Author:  [@JordiBolibar](https://discourse.julialang.org/u/JordiBolibar)
#### Post date: [July 4, 2023, 12:39pm UTC](https://discourse.julialang.org/t/large-vs-small-packages/9447/23 "2023-07-04T12:39:30Z")
Yes, I think splitting a large package into several ones makes more sense than just creating submodules in terms of performance. In a language like Python, one would just create submodules and import whatever is needed. Due to precompilation, in Julia it makes much more sense to split the package in multiple ones to avoid precompiling unnecessary stuff at the beginning.
[Previous page](https://discourse.julialang.org/t/large-vs-small-packages/9447.md?page=1)