this post was submitted on 21 Oct 2023
52 points (90.6% liked)

Rust

7232 readers
15 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] SpaceNoodle@lemmy.world 6 points 2 years ago (4 children)

Referring to lazy Python as "baseline" is a joke.

[–] snaggen@programming.dev 10 points 2 years ago* (last edited 2 years ago) (1 children)

But isn't it kind of obvious that if you are able to do 180k times improvement, then the baseline is probably not very impressive to begin with. Still, that doesn't take away that the optimizations were impressive, and that it was interesting to read about it.

[–] Turun@feddit.de 4 points 2 years ago (1 children)

I think your last sentence has one negation too much.

If it was interesting to read about it, then the criticism did not take away that the optimizations were impressive.

[–] snaggen@programming.dev 4 points 2 years ago

Fixed it.... I come from a language culture were we like our negations :) Also, not native english speaker, so combine the two and you are in for a ride!

[–] Sigmatics@lemmy.ca 5 points 2 years ago

Yeah, this one really had me scratching my head:

✓Note: there are lots of ways we could make the Python code faster, but the point of this post isn’t to compare highly-optimized Python to highly-optimized Rust. The point is to compare “standard-Jupyter-notebook” Python to highly-optimized Rust.

[–] eager_eagle@lemmy.world 4 points 2 years ago (1 children)

Yet it's a fine baseline. The actual speedup for switching to rust was 8x, the rest was all about changing data structures, using SIMD, parallelism and batching.

I think it's a great baseline. Within academic context, Python (and perhaps Matlab) are extremely common for data analysis. I doubt many would transition code to other languages unless strictly needed such as the case in the article. Showing how to "simply" speed up code like the article does is a great way to snag speed even if you don't analyze timing, and just replicate steps from this article.

Having done stuff myself as part of research, and having people I know go from developer jobs to research jobs, I can safely say scientists generally do not make good code. Regardless of language. An article like this gives good steps to take from start to end, and would be a valuable tool in a possible transition to better code.

[–] bluGill@kbin.social 3 points 2 years ago

With rust is the joke as if you couldn't do it otherwise. Maybe c would be only 179,999x faster, or FORTRAN 180,001x, (numbers made up). Python could probably be made 60,000x faster as well.