# Containerized application without recompilation at startup

**URL:** <https://numba.discourse.group/t/containerized-application-without-recompilation-at-startup/1637>\
**Category:** Support: How do I do ...?\
**Created:** [November 11, 2022, 8:27am UTC](https://numba.discourse.group/t/containerized-application-without-recompilation-at-startup/1637 "2022-11-11T08:27:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![nelson2005](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/nelson2005/32/47_2.png) [@nelson2005](https://numba.discourse.group/u/nelson2005)\
**Post date:** [November 14, 2022, 3:34pm UTC](https://numba.discourse.group/t/containerized-application-without-recompilation-at-startup/1637/5 "2022-11-14T15:34:37Z")

</div>

Glad you solved it! Another option might be possibly patching the timestamp on the save-side?  
Kind-of-related to your objmode timing, [this](https://numba.discourse.group/t/profiling-with-a-decorator-and-njit/55/21) discussion has @stuartarchibald’s nifty implementation of doing timing with the stdlib.

---

_[View the full topic](https://numba.discourse.group/t/containerized-application-without-recompilation-at-startup/1637)._