# Removing precompilation leads to lower allocations!?

**URL:** https://discourse.julialang.org/t/removing-precompilation-leads-to-lower-allocations/73621
**Category:** Performance
**Tags:** memory-allocation, precompilation
**Created:** [December 25, 2021, 6:15pm UTC](https://discourse.julialang.org/t/removing-precompilation-leads-to-lower-allocations/73621 "2021-12-25T18:15:25Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Salmon](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/salmon/32/22968_2.png) [@Salmon](https://discourse.julialang.org/u/Salmon)
#### Post date: [December 28, 2021, 2:20pm UTC](https://discourse.julialang.org/t/removing-precompilation-leads-to-lower-allocations/73621/2 "2021-12-28T14:20:41Z")

</div>

I’m bumping this since I am also interested in the answer.  
A while ago I have posted a similar question to this:

> [@A few basic questions about Precompilation](https://discourse.julialang.org/t/a-few-basic-questions-about-precompilation/71545):
>
> Hi everyone, I have recently tried with little success to add a precompilation step to my own package project and hope someone can help me clarify a few problems. In this post it is explained that one can precompile methods by calling precompile(method, (types...), however making it work in practice seems quite cumbersome. In particular, it is pointed out that the compiler cannot really precompile functions called within method without further steps. If I have a lot of functions is it rea…

I think it ultimately has to do with the fact that precompilation needs more than to just call a typical use case function, apparently you also have to explicitly specify input types (?).  
At least that was my takeaway so far, hopefully someone who knows more on this can enlighten us here 🙂

---

_[View the full topic](https://discourse.julialang.org/t/removing-precompilation-leads-to-lower-allocations/73621)._