# Improving Numba for CPU workloads

**URL:** <https://numba.discourse.group/t/improving-numba-for-cpu-workloads/3000>\
**Category:** Numba\
**Created:** [May 22, 2025, 9:42am UTC](https://numba.discourse.group/t/improving-numba-for-cpu-workloads/3000 "2025-05-22T09:42:15Z")\
**Posts on this page:** 1\
**Showing post:** 8

<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:** [May 26, 2025, 4:25pm UTC](https://numba.discourse.group/t/improving-numba-for-cpu-workloads/3000/8 "2025-05-26T16:25:57Z")

</div>

> [@yashssh](#):
>
> that might be bug in Numba and I remember seeing similar threads before, can you point me to or share a reproducer for a function with questionable compile time?

Lots of [examples](https://numba.discourse.group/t/long-compilation-times-for-simple-but-long-functions/1611) on the [net](https://stackoverflow.com/questions/77667746/numba-compilation-time-exponentially-exploding-can-optimization-level-be-confi).  
The program I work on daily takes on the order of an hour to compile.

I understand the compilation is entirely single threaded, so perhaps that’s part of a potential solution

---

_[View the full topic](https://numba.discourse.group/t/improving-numba-for-cpu-workloads/3000)._