aws-lambda-python-runtime-interface-client VS Numba

There is an AWS provided runtime client that will probably work with Python 3.11, but if not the API is small enough to roll your own. Or generate one with the OpenAPI Spec they provide.

Let's see what's happening here. We initiate a multi-phase build to reduce the size of our final image. On the FROM lines we choose which Python version we want to use for our runtime. If you wanted to work with Python 3.10 then you could simply replace the 3.11 part with 3.10. As a last step of the first build phase we install awslambdaric, which is the AWS Lambda Runtime Interface Client which makes sure that the Lambda environment is able to communicate with our own code. In the 2nd stage we simply copy the runtime interface client into our final image.

Yep. In fact, I recently had to deal with this monstrosity https://pypi.org/project/awslambdaric whose setup.py invokes a shell script https://github.com/aws/aws-lambda-python-runtime-interface-c...

That shell script runs 'make && make install' on a couple of bundled dependencies, but in principle it could do anything https://github.com/aws/aws-lambda-python-runtime-interface-c...

AWS has open-sourced some of the Lambda runtimes you might be using on a day-to-day basis. You can find the Go, Python and Node Lambda runtimes on their GitHub. I encourage you to go out and explore those repositories. There is much to learn about how the code you are writing and deploying is run.

Around the same time, I discovered Numba and was fascinated by how easily it could bring huge performance improvements to Python code.

Simulations are, at least in my experience, numba’s [0] wheelhouse.

[0]: https://numba.pydata.org/

That's very cool. Numba introduces just-in-time compilation to Python via decorators and its sole reason for being is to turn everything it can into abstract syntax trees.

A super-fast backtesting engine built in NumPy and accelerated with Numba.

Regarding speed, I don't agree this is a good argument against Python. For example, it seems no one here has yet mentioned numba, a Python JIT compiler. With a simple decorator you can compile a function to machine code with speeds on par with C. Numba also allows you to easily write cuda kernels for GPU computation. I've never had to drop down to writing C or C++ to write fast and performant Python code that does computationally demanding tasks thanks to numba.

Just for reference,

* Nuitka[0] "is a Python compiler written in Python. It's fully compatible with Python 2.6, 2.7, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, and 3.11."

* Pypy[1] "is a replacement for CPython" with builtin optimizations such as on the fly JIT compiles.

* Cython[2] "is an optimising static compiler for both the Python programming language and the extended Cython programming language... makes writing C extensions for Python as easy as Python itself."

* Numba[3] "is an open source JIT compiler that translates a subset of Python and NumPy code into fast machine code."

* Pyston[4] "is a performance-optimizing JIT for Python, and is drop-in compatible with ... CPython 3.8.12"

[0] https://github.com/Nuitka/Nuitka

[1] https://www.pypy.org/

[2] https://cython.org/

[3] https://numba.pydata.org/

[4] https://github.com/pyston/pyston

For the benefit of future readers: https://numba.pydata.org/

Taichi (similar to numba) is a python library that allows you to write high speed code within python. So your program consists of slow python that gets interpreted regularly, and fast python (fully type annotated and restricted to a subset of the language) that gets parallellized and jitted for CPU or GPU. And you can mix the two within the same source file.