Optimizing Python Performance using Numba JIT and Nuitka AOT Compilation

     In the world of programming, optimizing performance is a continuous pursuit, particularly when dealing with compute-intensive tasks. Developers often turn to Just-In-Time (JIT) compilation and Ahead-Of-Time (AOT) compilation techniques to achieve substantial performance gains.

In this case Selective Compilation Approach was used for using Numba with Nuitka

     Selective Compilation approach is to use Numba JIT selectively, only applying it to the parts of the codebase that are not compiled with Nuitka. This allows developers to reap the benefits of Numba's performance enhancements for specific sections while still leveraging Nuitka's AOT compilation for the rest of the codebase.

My Workaround

     To circumvent the compatibility roadblocks, we've ventured into a workaround centered on selective compilation. This innovative approach treats Numba-optimized functions as script code, which can be executed using Python's exec() function. By mapping the executed functions to Python objects, I've managed to bridge the gap between Numba JIT and Nuitka AOT, effectively harmonizing their strengths.

1. Function Definitions: Craft the Numba-optimized functions within dedicated .py files. These functions encapsulate intricate calculations or data manipulations that stand to benefit from Numba's performance enhancements.

2. Script Execution: Within the Nuitka-compiled codebase, employ exec() to execute the Python code stored in the separate .py files. This triggers Numba JIT compilation at runtime, dynamically optimizing the functions.

3. Function Mapping: Create a mapping object that associates function names with the dynamically optimized functions. This object serves as the bridge between the Numba JIT-optimized functions and the Nuitka AOT-compiled code.

4. Function Invocation: With Numba's JIT compilation applied, you can effortlessly invoke the Numba-optimized functions using the function objects stored in the mapping object. The performance gains from Numba's enhancements are now fully accessible.

Code Obfuscation

     To further enhance the integration of Numba JIT and Nuitka AOT, we introduce the concept of code obfuscation. Code obfuscation involves the transformation of human-readable code into a less understandable form while retaining its functionality. This process can help safeguard your intellectual property by making it more challenging for unauthorized users to reverse-engineer or understand your code.

1. Function Definitions and Code Obfuscation: Begin by defining your Numba-optimized functions within dedicated .py files. To obfuscate this code, compile these .py files into .pyc files using the marshal module. This step transforms the human-readable code into a bytecode representation that is less intuitive to interpret.

2. Script Execution with Obfuscated Code: Within the Nuitka-compiled codebase, use exec() to execute the obfuscated code stored in the .pyc files. This activates the Numba JIT compilation dynamically, enhancing the performance of the functions.

3. Function Mapping and Invocation: As before, create a mapping object linking function names to the dynamically optimized functions. You can then seamlessly invoke these functions using the function objects from the mapping object.

Benchmarking

     To complete our approach, we incorporate benchmarking by performing calculation on following function.

def sum_of_squares_py(n):
    result = 0
    for i in range(1, n + 1):
        result += i * i
    return result

By comparing different scenarios from pure Python approach, Numpy approach, and Numba approach as following parameters.

1. Pure Python Interpreter Benchmark: Measure the execution time of critical sections using the pure Python interpreter as a baseline.

2. Numba with Python Interpreter Benchmark: Benchmark the execution time after applying Numba JIT optimization in combination with the Python interpreter.

3. Numba with Python Interpreter Benchmark with Code Obfuscation: Benchmark execution time after applying Numba JIT optimization with the Python interpreter and code obfuscation .pyc.

4. Numba with Nuitka Benchmark: Measure the execution time after implementing Numba JIT optimization and Nuitka AOT compilation.

5. Numba with Nuitka Benchmark with Code Obfuscation: Measure execution time after implementing Numba JIT optimization, Nuitka AOT compilation, and code obfuscation .pyc.

6. Optimized Functions with NumPy Benchmark: Extend the benchmarking to include optimized functions utilizing NumPy for enhanced performance.

In this step, we employ the timeit.timeit module to measure elapsed time, iterating the process 10 times for enhanced accuracy.

Result

     We evaluate the performance of various optimization scenarios to gain insights into the effectiveness of our approach. Among these scenarios, the Pure Python Interpreter stands out as the baseline, revealing intriguing performance trends that shed light on the impact of our strategy. \ \

      * Showed data not include the initial "warm-up" time \      ** Numpy unable to allocate memory for an array with data type int64

1. Pure Python Interpreter: When using the pure Python interpreter, the execution time tends to increase linearly as the workload intensifies. This behavior is expected, as the interpreter handles code execution in a straightforward, sequential manner. As the workload grows, the interpreter's inherent overhead becomes more pronounced, resulting in a predictable increase in execution time.

2. Numpy Performance Anomaly: Interestingly, the benchmarking results indicate that the performance of NumPy is worse than that of the pure Python interpreter for small workloads. This initial dip in performance might stem from the additional overhead introduced by NumPy array manipulation operations, which could outweigh any performance benefits gained from optimized array computations. However, as the workload increases, NumPy performance stabilizes and remains consistently better than the pure Python interpreter for input sizes up to 2¹⁶. During this phase, NumPy leverages its optimized array manipulation operations to provide notable performance gains. However, beyond the input size of 2¹⁶, a shift in behavior is observed. At this point, NumPy performance starts to degrade, and the execution time begins to increase linearly, mirroring the behavior exhibited by the pure Python interpreter. This shift could be attributed to various factors, including the inherent overhead of NumPy sophisticated array operations and increased memory usage as the input size grows.

3. Numba Consistently Lower Execution Time: Across all scenarios, Numba demonstrates significantly lower execution times compared to both the pure Python interpreter and NumPy. This performance improvement is consistent and becomes particularly pronounced as the workload increases. The initial "warm-up" time observed in the first Numba execution is due to the lazy compilation approach of Numba. Once the functions are compiled and cached, subsequent executions benefit from the compiled machine code, leading to reduced execution times.

4. Numba with Nuitka and Code Obfuscation: When combining Numba with Nuitka and code obfuscation in Python optimization strikes a delicate balance between performance, compatibility, and portability. While a minor performance trade-off may occur due to Nuitka and code obfuscation, the benefits in terms of enhanced code security, improved compatibility through stand-alone executables, and broader portability make this approach compelling, especially in scenarios where critical performance is vital.

Conclusion

     This workaround not only enhances code performance through dynamic and ahead-of-time compilation but also fortifies code security and expands compatibility and portability. While a marginal performance trade-off may occur, the broader benefits of safeguarding intellectual property, enabling compatibility across environments, and facilitating deployment on diverse platforms make this approach compelling, particularly when critical performance remains a priority.