# Reduce Compilation Time

**URL:** <https://numba.discourse.group/t/reduce-compilation-time/969>\
**Category:** Support: How do I do ...?\
**Created:** [October 18, 2021, 1:19pm UTC](https://numba.discourse.group/t/reduce-compilation-time/969 "2021-10-18T13:19:57Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![stuartarchibald](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/stuartarchibald/32/10_2.png) [@stuartarchibald](https://numba.discourse.group/u/stuartarchibald)\
**Post date:** [November 3, 2021, 10:40am UTC](https://numba.discourse.group/t/reduce-compilation-time/969/9 "2021-11-03T10:40:54Z")

</div>

> [@max9111](#):
>
> Do you know a “clean” method to determine if there are cached compilation results (and for which signatures) are available for a njit decorated function?

@max911 I’m not sure there is, it sounds like this could be useful though? Do you mean something like `some_jitted_function.has_cached(some_signature)`? There is a `.stats` property on the jitted functions which has the cache path and hits/misses, but this is only updated on invocation for given types.

---

_[View the full topic](https://numba.discourse.group/t/reduce-compilation-time/969)._