# Understanding precompilation and its limitations (reducing latency)

**URL:** <https://discourse.julialang.org/t/understanding-precompilation-and-its-limitations-reducing-latency/48294>\
**Category:** Internals & Design\
**Tags:** precompilation\
**Created:** [October 13, 2020, 11:40am UTC](https://discourse.julialang.org/t/understanding-precompilation-and-its-limitations-reducing-latency/48294 "2020-10-13T11:40:14Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![joa-quim](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/joa-quim/32/227_2.png) [@joa-quim](https://discourse.julialang.org/u/joa-quim)\
**Post date:** [December 28, 2020, 7:00pm UTC](https://discourse.julialang.org/t/understanding-precompilation-and-its-limitations-reducing-latency/48294/12 "2020-12-28T19:00:26Z")

</div>

`@sprintf` seems to contribute in large to the inference issues. See first [post of](https://discourse.julialang.org/t/ccall-printf-works-with-ints-but-not-with-floats-why/52487).  
If I replace the `@sprintf` call [here](https://github.com/GenericMappingTools/GMT.jl/blob/master/src/common_options.jl#L2497) by a call to `sprintf` in the C lib, it shaves me 1 sec in Time to First Plot.

---

_[View the full topic](https://discourse.julialang.org/t/understanding-precompilation-and-its-limitations-reducing-latency/48294)._