Why Python Is So Slow (And What Is Being Done About It) (thenewstack.io)

submitted 3 months ago by dominiquec@lemmy.world to c/python@programming.dev

47 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] sugar_in_your_tea@sh.itjust.works 15 points 3 months ago* (last edited 3 months ago)

I'd really like to see Rust fit in where C(++) does now for Python. I know some libraties do it (e.g. Pydantic), but it really should be more common. It should work really well with the GIL... (or the TIL or whatever the new one is)

[-] barnaclebutt@lemmy.world 4 points 3 months ago* (last edited 3 months ago)

Or you could use cython, which is much easier to integrate with a python project. It is only marginally slower than Rust but a little less safe. Numpy libraries are usually the fast. Numba is a little clunky, but can also speed up code. There's lots of options to speed up python code.

[-] sugar_in_your_tea@sh.itjust.works 2 points 3 months ago

Yup, Cython rocks.

You can also use numba if you just need to accelerate one part of the app. We did that with a heavy part of the app and our naïve Python (using numpy) was about as fast as our naïve Rust, but only when wr turned on parallel processing in numba (I could've easily beat it with parallel Rust, but that requires extra work and wouldn't fit as nicely into the rest of the app).

[-] MalReynolds@slrpnk.net 4 points 3 months ago

Sounds like an excellent idea, I'd be surprised if it isn't happening.

[-] sugar_in_your_tea@sh.itjust.works 3 points 3 months ago

Well, it is happening, I just don't know how "blessed" it is by Python maintainers (i.e. are Python releases blocked by Rust binding updates?). It's 100% possible today and there are projects that use Rust bindings, I just don't know how that fits in with Python development vs the C++ API.